[Bug 2084698] Autopkgtest regression report (livecd-rootfs/24.04.79)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted livecd-rootfs (24.04.79) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/24.04.79 (arm64, s390x)
livecd-rootfs/unknown (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Apparmor profile policy permstable32 component is missing in Jammy 6.8
  kernel

Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Noble:
  Fix Committed

Bug description:
  A CPC snap preseeding test on recent Jammy image build with 6.8 kernel.
  Jammy 6.8 kernel has additional component under policy:permstable32 and this is missing in 6.8 apparmor directly.

  [ Impact ]

  Boot will be slowed by ~200ms until this is resolved in livecd-rootfs

  [ Test Plan ]
  * Build a jammy cloud image with preseeded snaps with missing components under `permstable32` file
  * Boot an instance
  * Run `snap debug preseed`
  * Confirm there is nothing in seed-restart-system-key when running `snap debug preseeding` command

  [ Where problems could occur ]
  * Missing these components, images with 6.8 kernel will not be optimized for first boot deployments.

  [ Other Info ]

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