So did I understand this right: * In current xenial, cloud-init runs in late boot, so there is no principal ordering problem between cloud-init and networkd, other than that cloud-init.service should declare After=systemd-networkd.service similar to what it does for ifupdown (After=networking.service).
* Thus this would not be a blocker for Ubuntu Core 16 right now, and merely adding that After= should suffice for the moment. * This *is* an issue for 16.10/zesty as cloud-init.service runs in early boot and dbus/networkd can't. * This *will become* an issue for 16.04 as these cloud-init changes are meant to be backported soon. Will that happen for the Ubuntu Core 16 GA in a few days already? I. e. is this something which we need to crowbar in ASAP, or do we have some time to figure out a proper solution how to start networkd first, and dbus later on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
