Jammy's cloud-init doesn't work on lxd 4.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
High
|
Chad Smith |
Bug Description
When trying to boot a Jammy container on a host that uses lxd/4.0 the cloud-init there fails to work properly.
The result is, that a ssh key for authentication isn't inserted in the host, denying ssh access.
Upgrading to lxd/5.0 does works around this issue, which provides a newer interface, but isn't a solution as lxd/4.0 is an LTS of only a few years old.
For a complete log see: https:/
To reproduce, install the lxd 4.0/stable snap on a machine, configure it to inject a ssh key, and try to launch an jammy container there. One won't be able to ssh into the container.
An extensive thread about this can be found at: https:/
Changed in cloud-init: | |
importance: | Critical → Undecided |
Changed in cloud-init: | |
status: | Triaged → New |
Changed in cloud-init: | |
status: | In Progress → Fix Committed |
Reproduced with:
```sh
lxc launch ubuntu-daily:focal fvm --vm
lxc shell fvm
snap list lxd
lxd init --minimal
lxc launch ubuntu-daily:jammy j
lxc exec j -- cloud-init status --wait
$ lxc exec j -- grep -i warning /var/log/ cloud-init. log sources. DataSourceLXD. DataSourceLXD' > failed py[WARNING] : Running ['netplan', 'apply'] resulted in stderr output: Failed to connect system bus: No such file or directory message. py[WARNING] : Used fallback datasource
2023-01-10 10:29:12,936 - util.py[WARNING]: Getting data from <class 'cloudinit.
2023-01-10 10:29:14,169 - activators.
2023-01-10 10:29:27,476 - cc_final_
$ lxc exec j -- grep -i exception /var/log/ cloud-init. log InvalidMetaData Exception( sources. InvalidMetaData Exception: Invalid HTTP response [404] from http:// lxd/1.0/ devices: 404 page not found
raise sources.
cloudinit.
```