Public bug reported:
Preseeding with the 7.2 kernel fails on stonking since the roll due to
an `apparmor` feature mismatch
[ Impact ]
When building Ubuntu images with the linux-{aws,azure,gcp,etc} 7.2
kernel using `livecd-rootfs`, snap preseeding fails as there's a
mismatch between the kernel's `apparmor` capabilities and the
capabilities listed in the `livecd-rootfs` features directory. These
images now have a slower boot time (becuase the snaps are being seeded
at first boot instead of on image creation)
[ Test Plan ]
* Build a CPC (GCP, for example) image with the version of `livecd-rootfs`
proposed here
* Register the image in Google cloud
* Boot into the image and confirm that the `snap debug seeding` output doesn't
contain the `seed-restart-system-key`
[ Where problems could occur ]
There's a low risk of regressions since this is a pretty standard thing
we do every time the kernel rolls to a new version, and there isn't any
runtime changes for users. One potential issue is if the proposed
changes don't actually rectify the mismatch in the `apparmor` features,
which will cause the slow boot times to remain (and in that situation we
just check the `seed-restart-system-key` key to see what features are
missing and start the process again).
[ Other Info ]
* Only affects Stonking right now as that's the only release with the
`7.2` kernel
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2167455
Title:
apparmor feature mismatch for the 7.2 kernel in stonking
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2167455/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
