[Bug 2116199] Re: apparmor feature mismatch for 6.14 HWE kernel

Bryan Alexander 2116199 at bugs.launchpad.net
Wed Sep 3 20:58:34 UTC 2025


I have tested the updated livecd-rootfs package from both noble-proposed
(24.04.93) and plucky-proposed (25.04.27) and can confirm it fixes the
issue.

The test was performed by building an Oracle cloud image with the
livecd-rootfs packages in proposed and running it through the test
suite. The tests confirmed that the `snap debug seeding` output no
longer contains the "seed-restart-system-key" key, confirming the fix is
working as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2116199

Title:
  apparmor feature mismatch for 6.14 HWE kernel

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Noble:
  Fix Committed
Status in livecd-rootfs source package in Oracular:
  Won't Fix
Status in livecd-rootfs source package in Plucky:
  Fix Committed
Status in livecd-rootfs source package in Questing:
  Fix Released

Bug description:
  Preseeding with the HWE 6.14 kernel fails due to AppArmor feature
  mismatch.

  [ Impact ]

  When building Ubuntu images with the HWE 6.14 kernel using livecd-
  rootfs, snap preseeding fails since there is a mismatch between the
  kernel's AppArmor capabilities and the capabilities listed in livecd-
  rootfs. As a result, these images have slower boot times as snaps are
  being seeded at first boot instead of image creation.

  [ Test Plan ]

  * Build an image with livecd-rootfs
  * Register the image on the cloud
  * Boot into the image
  * Check that "snap debug seeding" output doesn't contain the "seed-restart-system-key" key. Otherwise, check the `seed-restart-system-key` to see what features are missing.

  [ Where problems could occur ]

  The risk of regressions is minimal since we have previously backported
  similar changes a couple of times, and there should not be any runtime
  changes for end-users. One potential problem is if the proposed
  changes do not properly rectify the mismatch in the AppArmor features,
  which will cause the slow boot times to remain.

  [ Other Info ]
  * This bug affects both Noble and Questing
  * a similar SRU we did already is https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2037567

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2116199/+subscriptions




More information about the foundations-bugs mailing list