Can we do a SRU of https://github.com/canonical/snapd/commit/079605bdacc82243efdd44ec6d81bc4a93d2859f with some priority?
In the latest LXD image for jammy, the preinstalled snapd deb is 2.71+ubuntu22.04 and seeded snapd is 2.71 so the deb version is used and it hits to this issue. $ curl -s https://cloud-images.ubuntu.com/releases/jammy/release-20251021/ubuntu-22.04-server-cloudimg-amd64.squashfs.manifest | grep snapd snapd 2.71+ubuntu22.04 snap:snapd stable 25202 The latest daily image is fine since the preinstalled snapd deb is 2.71+ubuntu22.04 but the seeded snap is 2.72 so the snap version is used and can avoid this issue. $ curl -s https://cloud-images.ubuntu.com/jammy/20251023/jammy-server-cloudimg-amd64.squashfs.manifest | grep snapd snapd 2.71+ubuntu22.04 snap:snapd stable 25577 So when the next image gets released to the released stream, the issue is not going to be triggered. However, there is another SRU ongoing for 2.72 https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2124239 and once it completes for jammy then we will get into the same situation that the deb version of snapd is used. In my understanding, ultimately we need the patch above into the snapd deb itself so that it always works regardless of the revision of the seeded snapd snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127244 Title: Nested LXD is broken with snapd 2.71+ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2127244/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
