snapd service never completes on boot off focal cloudimg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When starting a VM using focal-server-
It reports the following on the console :
[FAILED] Failed to mount Mount unit for snapd, revision 7264.
See 'systemctl status snap-snapd-
Mounting Mount unit for snapd, revision 7264...
[FAILED] Failed to mount Mount unit for snapd, revision 7264.
See 'systemctl status snap-snapd-
here is the output of systemctl status :
root@focal-
● snap-snapd-
Loaded: not-found (Reason: Unit snap-snapd-
Active: failed (Result: exit-code) since Wed 2020-04-22 12:53:47 UTC; 1min 51s ago
Apr 22 12:53:47 focal-cloudinit systemd[1]: Mounting Mount unit for snapd, revision 7264...
Apr 22 12:53:47 focal-cloudinit mount[948]: mount: /snap/snapd/7264: mount failed: Operation not permitted.
Apr 22 12:53:47 focal-cloudinit systemd[1]: snap-snapd-
Apr 22 12:53:47 focal-cloudinit systemd[1]: snap-snapd-
Apr 22 12:53:47 focal-cloudinit systemd[1]: Failed to mount Mount unit for snapd, revision 7264.
journalctl has the following info :
root@focal-
● snap-snapd-
Loaded: not-found (Reason: Unit snap-snapd-
Active: failed (Result: exit-code) since Wed 2020-04-22 12:53:47 UTC; 1min 51s ago
Apr 22 12:53:47 focal-cloudinit systemd[1]: Mounting Mount unit for snapd, revision 7264...
Apr 22 12:53:47 focal-cloudinit mount[948]: mount: /snap/snapd/7264: mount failed: Operation not permitted.
Apr 22 12:53:47 focal-cloudinit systemd[1]: snap-snapd-
Apr 22 12:53:47 focal-cloudinit systemd[1]: snap-snapd-
Apr 22 12:53:47 focal-cloudinit systemd[1]: Failed to mount Mount unit for snapd, revision 7264.
root@focal-
-- Logs begin at Wed 2020-04-22 12:53:19 UTC, end at Wed 2020-04-22 12:55:26 UTC. --
Apr 22 12:53:34.403192 focal-cloudinit systemd[1]: Starting Snap Daemon...
Apr 22 12:53:35.838680 focal-cloudinit snapd[471]: AppArmor status: apparmor is enabled and all features are available
Apr 22 12:53:35.951309 focal-cloudinit snapd[471]: daemon.go:343: started snapd/2.44.3+20.04 (series 16; classic) ubuntu/20.04 (amd64) linu>
Apr 22 12:53:35.969592 focal-cloudinit snapd[471]: main.go:129: system does not fully support snapd: cannot mount squashfs image using "squ>
Apr 22 12:53:35.969592 focal-cloudinit snapd[471]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per>
Apr 22 12:53:36.145500 focal-cloudinit snapd[471]: helpers.go:105: error trying to compare the snap system key: system-key missing on disk
Apr 22 12:53:36.206822 focal-cloudinit systemd[1]: Started Snap Daemon.
Apr 22 12:53:42.697450 focal-cloudinit systemd[1]: snapd.service: Got notification message from PID 815, but reception only permitted for m>
Apr 22 12:53:44.393863 focal-cloudinit snapd[471]: handlers.go:495: Reported install problem for "snapd" as 4c06c57a-
Apr 22 12:53:47.602056 focal-cloudinit systemd[1]: snapd.service: Got notification message from PID 947, but reception only permitted for m>
Apr 22 12:53:48.057024 focal-cloudinit snapd[471]: handlers.go:495: Reported install problem for "snapd" as already-reported
As a side effect, this blocks execution of the cloud-config & cloud-final services that depend on it.
As snapd (still, see bug 1796987) doesn't log to Ubuntu's logging utility, you'll also need to gather information from their logging system. Run `snap changes` to get the ID of the change that failed, then run `snap change $id` to retrieve the logs from wherever snapd stores them.