[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-0ubuntu4

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

  * Cherry-pick upstream fix to start before systemd-networkd (LP:
#1772137)

 -- Julian Andres Klode <juliank at ubuntu.com>  Fri, 25 May 2018 16:08:00
+0200

** Changed in: networkd-dispatcher (Ubuntu)
       Status: In Progress => 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:
  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.

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