Public bug reported:
networkd-dispatcher's systemd unit has default dependencies, which means
it starts much, much too late to have any effect for interfaces brought
up by networkd at boot (since the events are missed, and not replayed).
We should instead have systemd unit dependencies like this (replicating
systemd-networkd's own):
[Unit]
Description=Dispatcher daemon for systemd-networkd
DefaultDependencies=no
After=systemd-udevd.service network-pre.target systemd-sysusers.service
systemd-sysctl.service
Before=systemd-networkd.service
In local testing, this DTRT.
** Affects: networkd-dispatcher (Ubuntu)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: New
** Affects: networkd-dispatcher (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: networkd-dispatcher (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: networkd-dispatcher (Ubuntu)
Importance: Undecided => High
** Also affects: networkd-dispatcher (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772137
Title:
networkd-dispatcher starts too late to take effect on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1772137/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
