debcrafters-packages team mailing list archive

[Chengen Du <2115418@xxxxxxxxxxxxxxxxxx>]

On a bare metal machine from Oracle Cloud using iSCSI boot in an
IPv6-only environment, the initial DHCPv6 setup is performed by iPXE to
boot the system. Subsequently, systemd attempts to perform its own
DHCPv6 configuration, but this process fails due to a mismatch in prefix
length.

Specifically, the network link remains stuck in the “configuring” state
and does not transition to an active state. This occurs because systemd
assumes a default prefix length of 128, while iPXE may assign a
different value—64 in this case, as indicated by
/sys/firmware/ibft/ethernet0/prefix-len.

Unfortunately, there is no current workaround, as this inconsistency
between systemd's assumption and the actual configuration leads to a
persistent configuration failure.

-- 
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:
  Incomplete
Status in systemd source package in Oracular:
  Won't Fix
Status in systemd source package in Plucky:
  Incomplete
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