[Bug 1982218] Re: wait-online does not correctly identify managed links

[Nick Rosbrook]

Thanks for that additional information.

So, looking into this a bit, I am a bit tempted to just drop this patch
from Jammy. For one, I will be dropping this patch in the current cycle
because upstream has a patch[1] now that accomplishes the same goal in a
different way.

More importantly though, looking at bug 1728181 (for which this patch
exists), it's not clear to me that this ever worked exactly as it was
intended. I will follow up to try and find out what happened, but based
on the comments it sounds like the fix was incomplete and wasn't further
developed.

Testing on Lunar, this patch only works as intended when the --any flag
is specified, which I think is because when this patch was refreshed
over the years, it was not correctly adapted for the context.

TL;DR - I do think this is something we can address in the next Jammy
SRU, and AFAICT just dropping the patch should solve your issue.

[1]

** Tags added: systemd-sru-next

** Also affects: systemd (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Jammy)
       Status: New => Triaged

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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982218

Title:
  wait-online does not correctly identify managed links

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged

Bug description:
  Ubuntu's packaging of systemd-networkd-wait-online includes a patch
  (UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if
  none of the present links are managed by systemd-networkd.  However,
  the patch fails to identify links in the "configuring" state, which
  implies they are managed, but not yet fully online.  This undermines
  the purpose of systemd-networkd-wait-online with the --any option,
  since at the time the systemd-networkd-wait-online service is started,
  managed links are _likely_ in a configuring, but-not-yet-configured
  state.

  Please see the attached patch.  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/+subscriptions