Just to give a data point, the issue is NOT reproducible with KVM based
VM if I use a similar generation of images.
for image in e7984776b69d 16bce345862c; do
lxc launch -e --vm "ubuntu:$image" "vm-$image" \
-c user.user-data='#cloud-config
bootcmd: ["echo CLOUD-INIT BOOTCMD RUN ✅"]
runcmd: ["echo CLOUD-INIT RUNCMD RUN ✅"]
'
done
-> works for the both images.
e7984776b69d (20251001) with snapd 2.68.5+ubuntu22.04.1, lxd snap 31333
16bce345862c (20251017) with snapd 2.71+ubuntu22.04, lxd snap 35819
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2130710
Title:
regression: cloud-init modules-config doesn't run on jammy due to
stuck snapd.seeded.service job
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2130710/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
