Jan, the fix is available upstream but not yet rolled out to existing
Ubuntu series. They're expected to roll out next week assuming no
additional issues are found.
The version number is 22.1-14-g2e17a0d6-0ubuntu1~YY.MM.2 and is
currently available from the -proposed pockets.
--
You received
The fix seems to still not be available in Ubuntu 18.04 and 20.04 as
well as their cloud images. The current images still list the LXD data
source before the OpenStack data source.
Is there any additional step needed to fix the issue in the LTS
releases?
--
You received this bug notification
This bug was fixed in the package cloud-init -
21.4-119-gdeb3ae82-0ubuntu1~22.04.1
---
cloud-init (21.4-119-gdeb3ae82-0ubuntu1~22.04.1) jammy; urgency=medium
* d/cloud-init.templates: Move LXD to back of datasource_list
* New upstream snapshot.
- tests: lsblk --json output
upstream commits landed which should resolve this issue on the next
published release of cloud-init v. 22.1. Expectation is within the next
3 weeks this fix will be in daily Ubuntu images.
- upstream commit reordering LXD datasource detecting priority to after
OpenStack:
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959118
Title:
We use nova-compute-lxd to run OpenStack "VMs" not as libvirt+QEMU
virtual machines, but as LXD containers. The nova-compute-lxd connects
to the local LXD daemon and creates containers, using a rootfs image
from Glance, and attaching it to networks managed by Neutron (VXLANs in
our case). As far
The intent was not to change LTS behavior, so yes, we will modify the
behavior accordingly.
Can you help me understand your use case so we know what needs to
change? Previous to this LXD Datasource, we expected LXD containers to
be identified to cloud-init using the NoCloud datasource. It sounds
