canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #01699
[Bug 1878225] Re: 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
Looks like we are hit by a very similar issue (on amd64). Me and a
colleague are having problems launching both ubuntu:22.04 and
ubuntu:20.04 LXC containers since last week. Seems like someone else had
asked about this on askubuntu.com too recently:
https://askubuntu.com/questions/1484049/lxd-ubuntu-image-startup-issue-
snap-lxd-activate-service-not-found. This response is by my colleague:
https://askubuntu.com/a/1489496/148223. Also asked about on
https://discourse.ubuntu.com/t/ubuntu-22-04-and-20-04-containers-stuck-
in-system-is-booting-up-state/39470/4.
We are yet to find a way of reproducing it outside our own machines
though. I tried setting up LXD on an internal server and there it works
perfectly fine, so it's definitely not broken everywhere.
I'm on Ubuntu 22.04 with LXD 5.18-da72b8b.
--
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