artful images hang when cloud-init is disabled due to no network config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
New
|
Low
|
Unassigned |
Bug Description
Modified the artful image to disable cloud-init like so:
qemu-img create -f qcow2 -b artful-
THis prevents cloud-init from running.
Boot takes many minutes and eventually times out with:
[ OK ] Started LXD - container startup/shutdown.
[ *** ] A start job is running for Wait for… to be Configured (49s / no limit) [** ] A start job is running for Wait for…e Configured (1min 37s / no limit)s
ystemd-
systemd-
systemd-
[ **] A start job is running for Wait for…be Configured (2min 1s / no limit)R
eceived SIGCHLD from PID 514 (systemd-network).
Child 514 (systemd-network) died (code=exited, status=1/FAILURE)
systemd-
-online.service systemd-
/FAILURE systemd-
systemd-
[FAILED] Failed to start Wait for Network to be Configured.
See 'systemctl status systemd-
systemd-
network-
network-
Without cloud-init which normally would emit a fallback network config, there isn't any network configuration in the image. systemd-
Previously images shipped with the 'networking' service which only waited until at least one of the *configured* interfaces were online; it queried ifupdown (via ifquery) to see which ones were configured.
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.
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).