after the upload of `snapd (2.53~pre1.git19b68f708)`, I see that snap
pre-seed optimizations aren't completing properly. the `seed-restart-
system-key` is now a call seen in `snap debug seeding`
'seed-restart-system-key': {'apparmor-features': ['caps', 'dbus',
'domain', 'file', 'mount', 'namespaces', 'network', 'network_v8',
'policy', 'ptrace', 'query', 'rlimit', 'signal'], 'apparmor-parser-
features': ['qipcrtr-socket', 'unsafe'], 'apparmor-parser-mtime':
1628490219, 'build-id': '62fa24aa378519ac08950d814427f03cc6ef1ee5',
'cgroup-version': '2', 'nfs-home': False, 'overlay-root': '', 'seccomp-
compiler-version': '59f5ac9a4838ef078f5b3f464f7669f76fddeab0 2.5.1
80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c bpf-
actlog', 'seccomp-features': ['allow', 'errno', 'kill_process',
'kill_thread', 'log', 'trace', 'trap', 'user_notif'], 'version': 10}
the helpful message in our tests state:
```
snap debug seeding' output (on stdout) contained
'seed-restart-system-key'. This indicates a kernel feature mismatch between
the running kernel and the feature set hard-coded in livecd-rootfs
for this image. Boot will be slowed by ~200ms until this is resolved
in livecd-rootfs.
Check the debug logs for /sys/kernel/apparmor/features/* and
/proc/sys/kernel/seccomp/actions_avail to update livecd-rootfs.
This failure can be ignored when publishing images with critical fixes.
```
I know the upload changed some seccomp profiles, so it may be that
something has changed in a way that's incompatible with livecd-rootfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
