[Bug 1772137] Re: networkd-dispatcher starts too late to take effect on boot

[Launchpad Bug Tracker]

This bug was fixed in the package networkd-dispatcher - 1.7-0ubuntu6

---------------
networkd-dispatcher (1.7-0ubuntu6) cosmic; urgency=medium

  * networkd-dispatcher.conf: Run startup triggers by default (LP:
#1772137)

 -- Julian Andres Klode <julian.klode at canonical.com>  Tue, 19 Jun 2018
11:19:39 +0200

** Changed in: networkd-dispatcher (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  networkd-dispatcher starts too late to take effect on boot

Status in networkd-dispatcher package in Ubuntu:
  Fix Released
Status in networkd-dispatcher source package in Bionic:
  Triaged

Bug description:
  [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):

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1772137/+subscriptions