** Description changed: A CPC test build of noble with the 6.17 `-proposed` kernel uncovered that the AppArmor profiles are missing for 6.17 in livecd-rootfs, leading to fall back to the "generic" AppArmor profiles. This leads to `snap debug seeding` outputting a filled `seed-restart-system-key` dict [0] after first boot. [ Impact ] Boot will be slowed in the clouds by about ~200ms until this is resolved [ Test Plan ] * Build a noble cloud image with the 6.17 kernel (either normally or from `-proposed` if it hasn't migrated yet) * Boot and run `snap debug seeding` * Ensure that the output doen't include `seed-restart-system-key` [ Where problems could occur ] * If this fix has other/new problems `snap debug seeding` will just continue to report `seed-restart-system-key` (i.e. there shouldn't be any other fallout) [ Other Info ] CPC blocks image publication on a test that ensures that snaps are preseeded. As a result this will block noble image publication once the kernel becomes the HWE kernel/migrated from `-proposed` + + [0]: https://pastebin.ubuntu.com/p/sMFHVRq8Mb/
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141707 Title: AppArmor profiles missing for noble kernel 6.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2141707/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
