** Changed in: lxd (Ubuntu Impish)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
> This should fix the problem:
https://github.com/lxc/distrobuilder/pull/476
wow...all those 'fixes' lxd is adding look like things will continue to
break in bad ways, like this bug. ouch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: systemd (Ubuntu Impish)
Status: Confirmed => Invalid
** Changed in: lxd (Ubuntu Impish)
Status: New => Fix Committed
** Changed in: lxd (Ubuntu Impish)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: auto-package-testing
Status: Incomplete
This should fix the problem:
https://github.com/lxc/distrobuilder/pull/476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
To m
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
To ma
So I can reproduce the problem even locally, using a simple:
`autopkgtest systemd --test-name=boot-and-services -- lxd
autopkgtest/ubuntu/impish/amd64`
When logging into the (stalled) system, while it is waiting for its
timeout I can see that eth0 gets configured, but then put in DOWN state.
Ther
Looks like I can at least reproduce the issue on an arm64 Canonistack
machine, utilizing an armhf container:
ubuntu@focal-arm64:~$ time autopkgtest systemd --test-name=boot-and-services -U
-- lxd autopkgtest/ubuntu/impish/armhf
[...]
autopkgtest [15:59:21]: test boot-and-services: [--
Seeing this failure on Focal now too.
Also seeing a similar problem on Bionic armhf which I'm wondering if it's
related to this failure. Bug 1932368
Difference is the test failing on Bionic is boot-smoke
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
bo
** Also affects: glibc (Ubuntu Impish)
Importance: Undecided
Status: Incomplete
** Also affects: dnsmasq (Ubuntu Impish)
Importance: Undecided
Status: Incomplete
** Also affects: isc-dhcp (Ubuntu Impish)
Importance: Undecided
Status: Incomplete
** Also affects: gdm3
I have added a badtest hint for this version, so that the many packages
blocked by this can become unblocked. But could somebody please take a
look? The hint is only for this version so the issue will come back with
the next systemd upload unless fixed.
(I'll reset systemd to "New" so that it app
Just to put the information on the bug, I reproduced this failure on a
Raspberry Pi, not a piece of the Scalingstack infrastructure in sight
;-)
As far as I can tell it looked as if it's timing out waiting for
network-online.target to become active. It seems as if installing
network-manager makes
** Tags added: fr-1435
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
To manage notifications about this bug go to:
https://bu
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
To manag
Marking auto package testing as affected based on @paelzer's observation
that it occurs only on Ubuntu's CI infra. I've also triggered the test
with hello to see current status and for confirmation.
** Also affects: auto-package-testing
Importance: Undecided
Status: New
--
You received
Also seeing this failure on Hirsute & Groovy systemd armhf through ADT:
https://autopkgtest.ubuntu.com/results/autopkgtest-
hirsute/hirsute/armhf/s/systemd/20210609_190755_3e0ab@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-
groovy/groovy/armhf/s/systemd/20210609_190741_7c920@/log.gz
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
bo
Also blocking isc-dhcp now, added a task
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As I said I tried to recreate this, but it worked.
It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container.
Upgrading the host to impish it Impish/5.11.0-16-generic still works fine.
It seems it only fails in autopkgtest infrastructure, not sure why yet
:-/
--
You received
I was adding a few of the blocked packages as incomplete tasks to have
this bug update-excuse show up in excuses. Right now until we know
better I'd consider this a systemd issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
20 matches
Mail list logo
