On Thu, Oct 27, 2016 at 5:59 AM, Martin Pitt <[email protected]> wrote:
> 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. > I suppose we could cherry pick the upstream snap create-user feature and other fixes but I expect the SRU of cloud-init to Xenial to include the change in ordering to enable running cloud-init earlier in boot; without resolved in 16.04 though the change isn't strictly needed but to keep the backported branch closer to trunk, I would expect those to come in. However, it does sound like it's reasonable to just add the After=systemd-networkd.service as you say; I can test this out now and confirm if that's sufficient to get a picture of what this should look like. > > * 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? > The official Ubuntu Core 16 GA images won't have cloud-init enabled by default. I'm currently working on a separate build of UC16 *with* cloud-init enabled, focusing on primary public cloud support. In this build, I'll include at least snapshot of cloud-init trunk as of a few days ago to include the snap create-user support needed for function. I can add a task against cloud-init for this bug and get a MR with the change to the cloud-init.service file after testing that the changes achieves the goal. > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 > -- 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/systemd/+bug/1636912/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
