Reading through the lxd issue log, it appears that a host networking issue/packaging issue triggered on upgrade; unrelated to cloud-init inside the containers. If you feel that cloud-init isn't doing something correct, please re-open this bug with new information.
Reading through the lxd issue log, it appears that a host networking issue/packaging issue triggered on upgrade; unrelated to cloud-init inside the containers. If you feel that cloud-init isn't doing something correct, please re-open this bug with new information.
Thanks.