Thank you very much, Jamie, for your detailed analysis in #15!
I've applied the same fix to isc-dhcp
https://launchpad.net/ubuntu/+source/isc-dhcp/4.4.1-2.3ubuntu3
We can consider SRUing this to Jammy and Impish, which are affect too.
But it doesn't feel too critical, as systemd-resolved usually wins the
race vs NetworkManager/dhclient, as you stated: "but with NetworkManager
as the netplan renderer, the dhclient script is called later and the dir
is created correctly."
I'm marking the systemd component as "Invalid", as the fix is needed in
other packages.
** No longer affects: systemd (Ubuntu Jammy)
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: isc-dhcp (Ubuntu)
Status: Triaged => Fix Committed
** Also affects: ifupdown (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: isc-dhcp (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Impish)
** Changed in: isc-dhcp (Ubuntu Impish)
Status: New => Triaged
** Changed in: isc-dhcp (Ubuntu Jammy)
Importance: High => Low
** Changed in: isc-dhcp (Ubuntu Impish)
Importance: Undecided => Low
** Changed in: ifupdown (Ubuntu Impish)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896772
Title:
systemd-resolved configures no Current Scopes on start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
