This bug was fixed in the package cloud-init -
22.1-14-g2e17a0d6-0ubuntu1~22.04.5
---------------
cloud-init (22.1-14-g2e17a0d6-0ubuntu1~22.04.5) jammy; urgency=medium
* d/p/cpick-be9389c6-Work-around-bug-in-LXD-VM-detection-1325:
cherry-pick be9389c6: Work around bug in LXD VM detection (#1325)
* d/p/cpick-30ccd51a-ds-identify-also-discover-LXD-by-presence-from-DMI:
cherry-pick 30ccd51a: ds-identify: also discover LXD by presence
from DMI
* d/p/pick-e3307e4d-ds-identify-detect-LXD-for-VMs-launched-from-host-with:
cherry-pick e3307e4d: ds-identify: detect LXD for VMs launched from
host with > 5.10 kernel (LP: #1968085)
-- James Falcon <james.fal...@canonical.com> Wed, 06 Apr 2022 16:48:16
-0500
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968085
Title:
Jammy: ds-identify: cloud-init disabled by generator due to inability
to detect LXD datasource when launched from Jammy host system
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1968085/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
