Comment 2 for bug 1728164

On Fri, Oct 27, 2017 at 8:16 PM, Mathieu Trudel-Lapierre <
<email address hidden>> wrote:

> I expect this is "stray" network-online.target.wants/ in livecd-rootfs
> for the ubuntu-cpc project. I *think* we don't want that to exist by
> default, and let systemd manage it on its own. ubuntu-cpc has that
> configuration file in includes.chroot/ that other flavors don't.
>

I don't think the service presence is at issue; it's whether or not the
wait-online service
can determine if there are any *configured* network devices; it should not
be
waiting for unconfigured (or if no devices are present at all).

>
> OTOH, cloud-init should be able to detect the NoCloud datasource when
> there is no metadata available anywhere and write some default
> configuration that makes some sense, such as when a metadata store is
> provided via some separately-attached storage (where at least in the
> cases I've tested, no specific network configuration was provided).
>

Cloud-init already does this. This case, cloud-init is disable; since it
does not run
it cannot provide a fallback network configuration.

And even if cloud-init did run and the image has no network devices,
network-wait-online
should not block unless it's waiting for configured devices to come up.

If there isn't already, there should be a systemd task around networkd
wait-online checking for
configured interfaces and only blocking if there is one to bring up.

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728164
>
> Title:
> artful images hang when cloud-init is disabled due to no network
> config
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-images/+bug/1728164/+subscriptions
>