This bug was fixed in the package systemd - 229-4ubuntu13
---------------
systemd (229-4ubuntu13) xenial; urgency=medium
[ Martin Pitt ]
* Backport graphical-session{,-pre}.target user units, for future usage from
snaps. (LP: #1640293)
* debian/rules: Clean up *.busname units. They are useless in 16.04 as they
will always be "condition failed" as kdbus has never existed. But they add
ordering constraints which make it impossible to start
systemd-networkd.service during early boot, which is an upcoming
requirement for cloud-init. (Part of LP: #1636912)
* Drop systemd-networkd's "After=dbus.service" ordering so that it can start
during early boot (for cloud-init.service). It will auto-connect to D-Bus
once it becomes available later, and transient (from DHCP) hostname and
timezone setting do not work in 16.04 anyway. (LP: #1636912)
[ Dan Streetman ]
* rules: introduce disk/by-id (wwid and model_serial) symlinks
for NVMe drives (LP: #1642903)
-- Martin Pitt <martin.p...@ubuntu.com> Thu, 24 Nov 2016 12:41:23
+0100
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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/systemd/+bug/1636912/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
