> cloud-init expects networking to be up, like 'networking.service'
before it runs..


I think it needs to make up its mind -- why does it want to run 
Before=network-online.target then? I thought the idea was that cloud-init is 
able to *provide* a network configuration (through the YAML). It seems to me 
that this might have to be split into two parts then -- one that can provide 
network config which runs early and does not require networking, and one that 
can use the network to configure other bits?

> So why shouldn't we use networkd-wait-online ?

You can use the program. I said that it might not be the best idea to
use After=s-n-wait-online.service, as that would block the entire cloud-
init.service and with it the entire boot (as cloud-init.service has very
strong dependencies) if there is no network available.

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to