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.
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: High => Medium
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636912
Title:
systemd-networkd runs too late for cloud-init.service (net)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1636912/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
