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

2021-06-13 Thread Sebastian Unger
Never mind. The scripts were in the wrong directory. /lib instead of /usr/lib. -- 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

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

2021-06-13 Thread Sebastian Unger
It appears this has been "unfixed" in focal? root@ttde-kvm6:~# systemctl cat networkd-dispatcher.service # /lib/systemd/system/networkd-dispatcher.service [Unit] Description=Dispatcher daemon for systemd-networkd [Service] Type=notify ExecStart=/usr/bin/networkd-dispatcher

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

2018-06-28 Thread Launchpad Bug Tracker
This bug was fixed in the package networkd-dispatcher - 1.7-0ubuntu3.2 --- networkd-dispatcher (1.7-0ubuntu3.2) bionic; urgency=medium * Revert "Cherry-pick upstream fix to start before systemd-networkd" * networkd-dispatcher.conf: Run startup triggers by default (LP: #1772137)

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

2018-06-25 Thread Julian Andres Klode
I added an example hook for routable, and started networkd-dispatcher on the system: with -3: Jun 25 11:08:58 bionic systemd[1]: Starting Dispatcher daemon for systemd-networkd... Jun 25 11:08:58 bionic networkd-dispatcher[4776]: No valid path found for iwconfig Jun 25 11:08:58 bionic

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

2018-06-21 Thread Brian Murray
Hello Steve, or anyone else affected, Accepted networkd-dispatcher into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /networkd-dispatcher/1.7-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this

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

2018-06-19 Thread Julian Andres Klode
** 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

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

2018-06-19 Thread 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 Tue, 19 Jun 2018 11:19:39 +0200 ** Changed in:

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

2018-06-19 Thread Julian Andres Klode
** Changed in: networkd-dispatcher (Ubuntu) Status: In Progress => Fix Committed -- 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

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

2018-06-01 Thread Francis Ginther
** Tags added: id-5b1030780cc11291cbe073af -- 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

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

2018-05-31 Thread Julian Andres Klode
Reverted the change for now, this needs more work. I guess we should reject the bionic SRU and figure out what to do. ** Changed in: networkd-dispatcher (Ubuntu Bionic) Status: In Progress => Confirmed ** Changed in: networkd-dispatcher (Ubuntu Bionic) Status: Confirmed => Triaged

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

2018-05-31 Thread Brian Murray
I'm going to hold off on approving the SRU until the cosmic issue has been investigated. -- 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

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

2018-05-31 Thread Scott Moser
I believe that this change has broken cosmic cloud-images. there is 'journalctl -o short-precise' output of a 20180530 image booted in kvm at http://paste.ubuntu.com/p/xhzxNc4QtR/ >From that you will see: May 31 15:54:35.838996 ubuntu systemd[1]: sysinit.target: Found ordering cycle on

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

2018-05-30 Thread Julian Andres Klode
** Description changed: - 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). + [Impact] + networkd-dispatcher's systemd unit

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

2018-05-27 Thread Francis Ginther
** Tags added: id-5affa8cf4534263e12fd1d5b -- 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

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

2018-05-25 Thread 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 Fri, 25 May 2018 16:08:00

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

2018-05-25 Thread Julian Andres Klode
Forwarded to https://github.com/craftyguy/networkd-dispatcher/issues/40, fixed in https://github.com/craftyguy/networkd- dispatcher/commit/87e5541c6039ab52c12031371147e8687a37bd10 - upstream also added an After=dbus.service (maybe it should be Wants/After=dbus.socket, though?) ** Bug watch added:

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

2018-05-24 Thread Julian Andres Klode
We probably also should replace WantedBy=multi-user.target with WantedBy =systemd-networkd.service so we only start it if systemd-networkd is started. Or add an Also=networkd-dispatcher.service to systemd- networkd.service; I don't know what I prefer. ** Changed in: networkd-dispatcher (Ubuntu)