[Bug 2147658] [NEW] AppArmor feature mismatch for 6.8 kernel

[Tomáš Virtus]

Public bug reported:

Preseeding with the 6.8 kernel fails due to AppArmor feature mismatch.

[ Impact ]

When building Ubuntu images with the linux-gke 6.8 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 n GKE 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 only Noble and so far only GKE images with linux-gke kernel since other cloud images use HWE kernel
* a similar SRU we did already is https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2116199

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/2147658

Title:
  AppArmor feature mismatch for 6.8 kernel

Status in livecd-rootfs package in Ubuntu:
  New

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

  [ Impact ]

  When building Ubuntu images with the linux-gke 6.8 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 n GKE 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 only Noble and so far only GKE images with linux-gke kernel since other cloud images use HWE kernel
  * a similar SRU we did already is https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2116199

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