UC16 devices ending up with snaps in broken state

[Jonathan Cave]

We have encountered a couple of devices that have ended up in state where multiple snaps have three revisions on the system with the oldest one in broken state and not mounted. This seems to prevent the device from refreshing the snap to a newer revision:

admin@1234567:~$ sudo snap refresh core --stable
error: cannot perform the following tasks:
- Setup snap "core" (11993) security profiles (cannot find installed snap "core" at revision 11993: missing file /snap/core/11993/meta/snap.yaml)

[Jonathan Cave (jocave)]

At this point I had started trying to recover the device so the core snap 11993 had been removed from the system. Here are the contents of:

/var/lib/snapd/snaps
/etc/systemd/system/*.mount

[Michael Vogt (mvo)]

So this looks like the mount unit and the snap file for the core 11993 snap got removed but it was not removed from the state. This is puzzling and worrying.

[Michael Vogt (mvo)]

Thanks! could you also (just for completes) attach /var/lib/snapd/state.json ?

[Maciej Borzecki (maciek-borzecki)]

Can you attach the output of `sudo cat /var/lib/snapd/state.json | jq '.data.snaps["core"]' or if it's not possible to install jq snap on the device, download state.json to your local host and run the jq command there. Please do not attach the whole state.json as it contains sensitive data.

[Launchpad Janitor (janitor)]

[Expired for Snappy because there has been no activity for 60 days.]