← Back to team overview

debcrafters-packages team mailing list archive

[Bug 2115418] Re: systemd-networkd-wait-online service times out in IPv6-only environments

 

Hello,
I tested the systemd with version 257.4-1ubuntu3.2 in the plucky-proposed package and confirmed it fixed the problem.
The testing steps I have followed:
1. Set up an IPv6-only environment with iSCSI boot.
2. Enable plucky-proposed repository and upgrade systemd package to 257.4-1ubuntu3.2
3. Run the networkctl command and verify that no links remain in the "configuring" state.
   # networkctl
  IDX LINK TYPE OPERATIONAL SETUP
  1 lo loopback carrier unmanaged
  2 ens300np0 ether routable configured
  3 ens340np0 ether off unmanaged

4. Restart the systemd-networkd-wait-online service and ensure that its status does not show error message:
   "Timeout occurred while waiting for network connectivity"
   # systemctl status systemd-networkd-wait-online
● 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: active (exited) since Tue 2025-09-09 05:38:03 UTC; 4s ago
 Invocation: 07c1e3f62c714a76851bca45a98ecece
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 4663 ExecStart=/lib/systemd/systemd-networkd-wait-online -i ens300np0:degraded (code=exited, status=0/SUCCESS)
    Process: 4664 ExecStart=/lib/systemd/systemd-networkd-wait-online --any --dns -o routable -i ens300np0 (code=exited, status=0/SUCCESS)
   Main PID: 4664 (code=exited, status=0/SUCCESS)
   Mem peak: 1.8M
        CPU: 28ms



** Tags removed: verification-needed-plucky
** Tags added: verification-done-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:
  Fix Committed
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



References