*** This bug is a duplicate of bug 1940791 ***
https://bugs.launchpad.net/bugs/1940791
Chad Smith was able to reproduce this while investigating #1940791, and
this appears to be the same root cause as #1940791, so I'm going to mark
this one as a duplicate.
** This bug has been marked a
Thanks for testing James. But that's different from what I'm seeing.
True full reproducer for me:
Host: Fedora 35
git clone https://github.com/virt-manager/virt-manager
cd virt-manager
wget
https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-disk-kvm.img
# change image
Thanks for the detailed bug report.
I used your reproducer steps, but I got a slightly different result. I'm
still not getting the NoCloud identification, but in my case, I can't
force ds-identify to identify it. In order for ds-identify to identify
NoCloud, it needs to see a "cidata" filesystem
Hi Cole, FYI I have yesterday pinged the cloud-init develpers about both to
check these cases.
I also added the extra bug task here.
And for bug 1940791 I have mentioned that I think it might have expired without
a real conclusion.
--
You received this bug notification because you are a member
The reporter of the virt-install bug also found this expired focal
cloud-images bug which sounds like the same root issue:
https://bugs.launchpad.net/cloud-images/+bug/1940791
If someone with more launchpad knowledge can route this report to the
correct place, please do. Would be nice to get this
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961832
Title:
jammy-server-cloudimg-amd64-disk-kvm.img NoCloud data
