Verified Jammy: Steps:
1. using bartender, built an image using the livecd-rootfs 2.765.41 code pulled from https://launchpad.net/ubuntu/+source/livecd-rootfs/2.765.41 bartender \ --hook-extras-branch jammy \ --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-rootfs/2.765.41/livecd-rootfs \ --build-provider aws \ --aws-keypair-name ${AWS_BUILD_KEY} \ --aws-profile image_builder \ -- \ --series jammy \ --project ubuntu-cpc \ --image-target qcow2 ### NOTE ### You don't have to provide hook-extras-branch build a qcow2. I just default to always using it... 2. untarred the contents 3. launched with QEMU qemu-system-x86_64 \ -cpu host -machine type=q35,accel=kvm -m 2048 \ -nographic \ -snapshot \ -netdev id=net00,type=user,hostfwd=tcp::2222-:22 \ -device virtio-net-pci,netdev=net00 \ -drive if=virtio,format=qcow2,file=livecd.ubuntu-cpc.img \ -cdrom cloud_init.iso \ -bios /usr/share/OVMF/OVMF_CODE.fd ### NOTE ### cloud-init.iso just adds my ssh key into the image. 4. logged in and ran `sudo snap debug seeding` sudo snap debug seeding seeded: true preseeded: true image-preseeding: 8.498s seed-completion: 1.823s 5. and just to double check, yes there are snaps snap list Name Version Rev Tracking Publisher Notes core20 20240111 2182 latest/stable canonical✓ base lxd 5.0.3-babaaf8 27948 5.0/stable/… canonical✓ - snapd 2.61.2 21184 latest/stable canonical✓ snapd ** Tags removed: verification-needed verification-needed-jammy ** Description changed: After the kernel roll to linux-gcp-5.15 to version 5.15.0-1051.59_20.04.1 the public cloud team pre publication test were failing on our snap_preseed_optimized test which checks to ensure that snaps are preseeded correctly This test checks the output of `snap debug seeding` to assert `seed- completion` is present and not empty. `` ❯ snap debug seeding seeded: true preseeded: true image-preseeding: 39.367s seed-completion: 1.335s ``` If `/var/lib/snapd/seed/seed.yaml` exists it also asserts that `preseeded` is present and not empty. With the recent kernel update this test is failing which indicates a kernel feature mismatch between the running kernel and the feature set hard-coded in livecd-rootfs for this image. Boot will be slowed by ~200ms until this is resolved in livecd-rootfs. This solution is to add a 5.15 apparmor configuration to the focal branch of livecd-rootfs The issue is also present with the recent 5.15 kernels in Jammy. Related bugs LP: #2031943 and LP: #2045384 [ Impact ] Boot will be slowed by ~200ms until this is resolved in livecd-rootfs [ Test Plan ] * for focal build any cloud image with preseeded snaps with HWE 5.15 kernel - * for jammy build any cloud image with preseeded snaps with up to date 5.15 kernel + * for jammy build any cloud image with preseeded snaps with up to date 5.15 kernel * boot - * run `snap debug preseed` + * run `snap debug seeding` * assert the test described above passes [ Where problems could occur ] * Similar patches already exist for later releases 6.2, 6.5 kernel etc. and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
