debcrafters-packages team mailing list archive

[Nick Rosbrook <2115418@xxxxxxxxxxxxxxxxxx>]

Regarding the bug in general:

It sounds like this bug condition specifically requires that DHCPv6 +
one other source request the same address. Have you figured out
precisely where the other configuration is coming from? Is it not
possible to simply workaround this issue by eliminating the other
configuration source?

Regarding the SRU documentation:

Please update the test plan to verify that systemd-networkd-wait-online
no longer times out.

I understand that the link state is the *minimal* reproducer, but the
described user impact is the systemd-networkd-wait-online service timing
out, so we should specifically test that condition, too.


** Changed in: systemd (Ubuntu Noble)
       Status: New => Incomplete

** Changed in: systemd (Ubuntu Plucky)
       Status: New => Incomplete

-- 
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.

  [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