The error at the top of the cloud-init-output.log appears to be a red herring. It's part of the init-local piece done by cloud-init asap after boot. I bootstrapped an controller on OpenStack, deployed the ubuntu charm --to lxd. The container did get an IP addr in this case, but also had the same error at the top of the cloud-init-output.log
Is it possible to get the following files from one of the containers exhibiting this issue:
/var/lib/cloud/instance/*
The error at the top of the cloud-init- output. log appears to be a red herring. It's part of the init-local piece done by cloud-init asap after boot. I bootstrapped an controller on OpenStack, deployed the ubuntu charm --to lxd. The container did get an IP addr in this case, but also had the same error at the top of the cloud-init- output. log
Is it possible to get the following files from one of the containers exhibiting this issue: cloud/instance/ *
/var/lib/