** Description changed: [Impact] 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): + [Test Case] + Start systemd-networkd / boot system with it, ensure the current status is replayed when networkd-dispatcher starts. + + [Regression potential] + The current status is replayed when the service is restarted, and more events run at boot, potentially causing slowdown/problems with hooks not expecting to receive an event a second time (after restart). That said, not replaying the current status on restart would mean we might lose important events during that window. + + [Original approach] + 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. - - [Test Case] - Start systemd-networkd / boot system with it, ensure networkd-dispatcher is started before it. - - Run 'journalctl -o short-precise | grep -i ordering'. There cannot be - any ordering cycles present. - - [Regression potential] - Slower boots as systemd-networkd will now only run after networkd-dispatcher.service, and that runs after dbus.service.
-- 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
