canonical-ubuntu-qa team mailing list archive

[John Chittum <1878225@xxxxxxxxxxxxxxxxxx>]

if the core issue is falling to snap pre-seeding, then, yes, there is a
reliance on matching kernel at build time of the squashfs and the build
system.

this is because we build the images in a chroot, and have to mount in
the apparmor features to the chroot. when launching a container with a
"mismatched" kernel, with snapd running, it may not have the matching
set of features. You can see this in the `apparmor-features` and
`apparmor-parser-features` under the `preseed` and `seed-restart` keys.

unfortunately, this is a limitation in snap preseeding right now, where
snapd has a hard requirement on knowing the kernel apparmor sets. here
are some links:

1. the function that must be called during build the validate the seed

https://git.launchpad.net/livecd-rootfs/tree/live-
build/functions?h=ubuntu/jammy#n759

2. the different kernel directories

https://git.launchpad.net/livecd-rootfs/tree/live-
build/apparmor?h=ubuntu/jammy

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/1878225

Title:
  Please remove lxd.snap from lxd images, as it fails to seed thus
  failing the first boot - snapd.seeded.service waits forever (?) to
  have snaps seeded in LXD on s390x and arm64

Status in Auto Package Testing:
  Triaged
Status in cloud-images:
  Invalid
Status in snapd:
  Triaged
Status in autopkgtest package in Ubuntu:
  Triaged
Status in lxd package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Invalid
Status in autopkgtest source package in Groovy:
  Triaged
Status in lxd source package in Groovy:
  Invalid
Status in snapd source package in Groovy:
  Invalid

Bug description:
  lxc launch ubuntu-daily:groovy gg-test
  lxc shell gg-test
  root@gg-test:~# service snapd.seeded status
  ● snapd.seeded.service - Wait until snapd is fully seeded
       Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; vendor preset: enabled)
       Active: activating (start) since Tue 2020-05-12 14:14:52 UTC; 30min ago
     Main PID: 249 (snap)
        Tasks: 10 (limit: 4704)
       Memory: 11.3M
       CGroup: /system.slice/snapd.seeded.service
               └─249 /usr/bin/snap wait system seed.loaded

  May 12 14:14:52 gg-test systemd[1]: Starting Wait until snapd is fully
  seeded...

  root@gg-test:~# systemctl list-jobs 
  JOB UNIT                                 TYPE  STATE  
  132 systemd-update-utmp-runlevel.service start waiting
  119 cloud-config.service                 start waiting
  122 snapd.seeded.service                 start running
  2   multi-user.target                    start waiting
  115 cloud-init.target                    start waiting
  1   graphical.target                     start waiting
  138 snapd.autoimport.service             start waiting
  121 cloud-final.service                  start waiting

  8 jobs listed.

  root@gg-test:~# journalctl -a | pastebinit
  https://paste.ubuntu.com/p/PtdcvvdKCM/

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1878225/+subscriptions