Activity log for bug #1772137

Date Who What changed Old value New value Message
2018-05-19 04:31:35 Steve Langasek bug added bug
2018-05-19 04:31:42 Steve Langasek bug added subscriber Dimitri John Ledkov
2018-05-19 04:31:48 Steve Langasek networkd-dispatcher (Ubuntu): assignee Julian Andres Klode (juliank)
2018-05-19 04:32:14 Steve Langasek networkd-dispatcher (Ubuntu): importance Undecided High
2018-05-19 04:32:20 Steve Langasek nominated for series Ubuntu Bionic
2018-05-19 04:32:20 Steve Langasek bug task added networkd-dispatcher (Ubuntu Bionic)
2018-05-24 09:55:38 Julian Andres Klode networkd-dispatcher (Ubuntu): status New In Progress
2018-05-24 09:55:45 Julian Andres Klode networkd-dispatcher (Ubuntu Bionic): status New Triaged
2018-05-24 09:55:51 Julian Andres Klode networkd-dispatcher (Ubuntu Bionic): importance Undecided High
2018-05-25 08:28:01 Julian Andres Klode bug watch added https://github.com/craftyguy/networkd-dispatcher/issues/40
2018-05-25 16:07:01 Launchpad Janitor networkd-dispatcher (Ubuntu): status In Progress Fix Released
2018-05-27 12:37:09 Francis Ginther tags id-5affa8cf4534263e12fd1d5b
2018-05-30 08:27:13 Julian Andres Klode 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. [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. [Regression potential] Slower boots as systemd-networkd will now only run after networkd-dispatcher.service, and that runs after dbus.service.
2018-05-30 08:28:12 Julian Andres Klode networkd-dispatcher (Ubuntu Bionic): status Triaged In Progress
2018-05-30 19:36:27 Nico van der Walt bug added subscriber Nico van der Walt
2018-05-31 17:11:14 Scott Moser 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. [Regression potential] Slower boots as systemd-networkd will now only run after networkd-dispatcher.service, and that runs after dbus.service. [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.
2018-05-31 17:12:58 Philip Roche bug added subscriber Philip Roche
2018-05-31 18:09:38 Julian Andres Klode networkd-dispatcher (Ubuntu Bionic): status In Progress Confirmed
2018-05-31 18:09:39 Julian Andres Klode networkd-dispatcher (Ubuntu Bionic): status Confirmed Triaged
2018-05-31 18:10:18 Julian Andres Klode networkd-dispatcher (Ubuntu): status Fix Released Triaged
2018-05-31 18:10:21 Julian Andres Klode networkd-dispatcher (Ubuntu): status Triaged In Progress
2018-06-01 12:34:12 Francis Ginther tags id-5affa8cf4534263e12fd1d5b id-5affa8cf4534263e12fd1d5b id-5b1030780cc11291cbe073af
2018-06-19 09:53:22 Julian Andres Klode networkd-dispatcher (Ubuntu): status In Progress Fix Committed
2018-06-19 10:34:13 Launchpad Janitor networkd-dispatcher (Ubuntu): status Fix Committed Fix Released
2018-06-19 15:07:24 Julian Andres Klode 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. [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). [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.
2018-06-21 19:48:29 Brian Murray networkd-dispatcher (Ubuntu Bionic): status Triaged Fix Committed
2018-06-21 19:48:32 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2018-06-21 19:48:35 Brian Murray bug added subscriber SRU Verification
2018-06-21 19:48:39 Brian Murray tags id-5affa8cf4534263e12fd1d5b id-5b1030780cc11291cbe073af id-5affa8cf4534263e12fd1d5b id-5b1030780cc11291cbe073af verification-needed verification-needed-bionic
2018-06-25 11:09:55 Julian Andres Klode tags id-5affa8cf4534263e12fd1d5b id-5b1030780cc11291cbe073af verification-needed verification-needed-bionic id-5affa8cf4534263e12fd1d5b id-5b1030780cc11291cbe073af verification-done verification-done-bionic
2018-06-28 07:18:28 Ɓukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2018-06-28 07:18:31 Launchpad Janitor networkd-dispatcher (Ubuntu Bionic): status Fix Committed Fix Released
2022-04-21 05:55:00 Arkadiy bug added subscriber Arkadiy