All autopkgtests for the newly accepted systemd (257.4-1ubuntu3.2) for plucky have finished running. The following regressions have been reported in tests triggered by the package:
apport/2.32.0-0ubuntu5.3 (amd64, arm64, ppc64el) avahi/0.8-16ubuntu2 (s390x) cups/2.4.12-0ubuntu1 (s390x) dbus-broker/36-1ubuntu0.25.04.1 (s390x) dracut/106-2ubuntu5 (amd64) gnome-remote-desktop/48.0-1 (s390x) incus/6.0.3-4 (armhf) initramfs-tools/0.147ubuntu1.1 (s390x) libsoup3/3.6.5-1ubuntu0.2 (ppc64el) linux-realtime/6.14.0-1010.10 (amd64) netplan.io/1.1.2-2ubuntu1.1 (arm64, s390x) samba/2:4.21.4+dfsg-1ubuntu3.4 (ppc64el) sks/1.1.6+git20210302.c3ba6d5a-4.1 (amd64, arm64, armhf, ppc64el, s390x) systemd/257.4-1ubuntu3.2 (amd64, ppc64el) util-linux/2.40.2-14ubuntu1.1 (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/plucky/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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2115418 Title: systemd-networkd-wait-online service times out in IPv6-only environments Status in cloud-images: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Noble: Triaged Status in systemd source package in Oracular: Won't Fix Status in systemd source package in Plucky: Fix Committed Status in systemd source package in Questing: Fix Released Bug description: [Impact] In an iSCSI boot scenario within an IPv6-only environment, the link remains in the "configuring" state when the DHCPv6-assigned address conflicts with an already configured address. Although network connectivity works as expected, this condition causes the systemd-networkd-wait-online service to time out during the boot process. [Fix] This issue has been resolved upstream. https://github.com/systemd/systemd/pull/37916 [Test Plan] 1. Set up an IPv6-only environment with iSCSI boot. 2. Run the networkctl command and verify that no links remain in the "configuring" state. 3. Restart the systemd-networkd-wait-online service and ensure that its status does not show the following: × systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/usr/lib/systemd/system/systemd-networkd-wait-online.service; enabled; preset: enabled) Drop-In: /run/systemd/system/systemd-networkd-wait-online.service.d └10-netplan.conf Active: failed (Result: exit-code) since Mon 2025-07-14 01:39:53 UTC; 3min 20s ago Docs: man:systemd-networkd-wait-online.service(8) Process: 6141 ExecStart=/lib/systemd/systemd-networkd-wait-online -i ens300np0:degraded (code=exited, status=1/FAILURE) Main PID: 6141 (code=exited, status=1/FAILURE) CPU: 6ms Jul 14 01:37:53 noble-bm systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured... Jul 14 01:39:53 noble-bm systemd-networkd-wait-online[6141]: Timeout occurred while waiting for network connectivity. Jul 14 01:39:53 noble-bm systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jul 14 01:39:53 noble-bm systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Jul 14 01:39:53 noble-bm systemd[1]: Failed to start systemd-networkd-wait-online.service - Wait for Network to be Configured. [Where problems could occur] The commit introduces a new member variable to track this specific condition and updates the link status accordingly. If any regressions occur, the link status may become incorrect, potentially causing unexpected behavior in the systemd-networkd-wait-online service. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2115418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
