So with the latter, removing this ordering would break the "UseHostname: yes" flag (when you receive/set your host name from what DHCP gives you), i. e. it would silently not work. We don't use that feature in the distro itself, but it would be a shame to break it for everyone even when cloud-init is not involved at all.
So this at least gives us a quick way out for 16.04 -- we can simply drop the "After=dbus.service" from systemd-networkd.service without much trouble, but for devel I'd at least discuss this with upstream.
The "networkd after D-Bus" ordering was introduced in https:/ /github. com/systemd/ systemd/ commit/ 1346b1f038 and later refined in https:/ /github. com/systemd/ systemd/ commit/ bcbca8291f .
So with the latter, removing this ordering would break the "UseHostname: yes" flag (when you receive/set your host name from what DHCP gives you), i. e. it would silently not work. We don't use that feature in the distro itself, but it would be a shame to break it for everyone even when cloud-init is not involved at all.
So this at least gives us a quick way out for 16.04 -- we can simply drop the "After= dbus.service" from systemd- networkd. service without much trouble, but for devel I'd at least discuss this with upstream.