[Bug 2143170] [NEW] AppArmor profiles missing for resolute kernel 6.19

[Jess Jang]

Public bug reported:

A CPC test build of resolute with the 6.19 kernel and test result
indicated that the AppArmor profiles are missing for 6.19 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.canonical.com/p/ydC43BWWMx/

Related issue: https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/2141707

** 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/2143170

Title:
  AppArmor profiles missing for resolute kernel 6.19

Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  A CPC test build of resolute with the 6.19 kernel and test result
  indicated that the AppArmor profiles are missing for 6.19 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.canonical.com/p/ydC43BWWMx/

  Related issue: https://bugs.launchpad.net/ubuntu/+source/livecd-
  rootfs/+bug/2141707

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