debcrafters-packages team mailing list archive

[Timo Aaltonen <2115418@xxxxxxxxxxxxxxxxxx>]

Hello Gauthier, or anyone else affected,

Accepted systemd into plucky-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/257.4-1ubuntu3.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Plucky)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-plucky

-- 
You received this bug notification because you are a member of
Debcrafters 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