[Bug 2036358] Autopkgtest regression report (systemd/249.11-0ubuntu3.11)
Ubuntu SRU Bot
2036358 at bugs.launchpad.net
Thu Sep 21 02:55:57 UTC 2023
All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.11) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
casync/2+20201210-1build1 (arm64, ppc64el)
dbus/1.12.20-2ubuntu4.1 (armhf)
libsoup3/3.0.7-0ubuntu1 (armhf)
linux-aws-6.2/6.2.0-1013.13~22.04.1 (arm64)
linux-lowlatency-hwe-5.19/5.19.0-1030.30 (arm64)
linux-lowlatency-hwe-6.2/6.2.0-1014.14~22.04.1 (arm64)
linux-nvidia-6.2/6.2.0-1010.10 (amd64)
linux-nvidia-tegra/5.15.0-1017.17 (arm64)
linux-nvidia-tegra-igx/5.15.0-1004.4 (arm64)
linux-xilinx-zynqmp/5.15.0-1023.27 (arm64)
mutter/42.9-0ubuntu4 (arm64)
netplan.io/0.106.1-7ubuntu0.22.04.2 (amd64, arm64, ppc64el, s390x)
stunnel4/3:5.63-1build1 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online now times out after jammy and lunar upgrade
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Jammy:
Fix Committed
Status in systemd source package in Lunar:
Fix Committed
Bug description:
[Impact]
When all interfaces are "not required for online", e.g. when they are
marked "optional: true" in netplan, systemd-networkd-wait-online will
timeout. Or, in other words, systemd-networkd-wait-online will timeout
even though all interfaces are ignored, hence none of them will ever
be marked as "ready." Depending on what units depend on network-
online.target, this can delay boot by 120 seconds (the default timeout
for systemd-networkd-wait-online).
[Test Plan]
1. Create a new LXD container. These instructions assume jammy is the
release, but the same can be done for lunar.
$ lxc launch ubuntu-daily:jammy jammy
$ lxc exec jammy bash
2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
so that eth0 is configured with "optional: true":
$ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like
$ cat /etc/netplan/10-lxc.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
dhcp-identifier: mac
optional: true
3. Re-generate and apply the netplan configuration.
$ netplan generate
$ netplan apply
4. Manually run systemd-networkd-wait-online, and observe that all
links are ignored, and the command times out:
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link lo(1)
Found link eth0(19)
lo: link is ignored
eth0: link is ignored
Timeout occurred while waiting for network connectivity.
[Where problems could occur]
This patch partially re-instates a patch remove in bug 1982218.
However, instead of exiting if all links are unmanaged, we exit if all
links are ignored in manager_configured(). If the patch was wrong, we
may re-introduce bug 1982218, so as part of this SRU verification,
that bug should be tested too. Any other regressions would also be
related to systemd-networkd-wait-online behavior.
[Original Description]
On Ubuntu 22.04 desktop system using network-manager and upgrading to
systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
logins (GDM, ssh, console) until it does time out. This seems to be
introduced by the change for
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
also mentioned the problem on Lunar.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions
More information about the foundations-bugs
mailing list