snapd.snap-repair.service fails to start on uc20

Bug #1879729 reported by Paul Larson on 2020-05-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
High
Samuele Pedroni

Bug Description

While testing the arm64 images on rpi, I noticed that the snapd.snap-repair.service does not start. It seems to be looking for /var/lib/snapd/seed/seed.yaml which does not exist. Here's the journalctl from the failure:

-- Logs begin at Tue 2019-11-19 12:24:26 UTC, end at Wed 2020-05-20 14:59:59 UTC. --
May 20 14:15:33 ubuntu systemd[1]: Starting Automatically fetch and run repair assertions...
May 20 14:15:33 ubuntu snap-repair[817]: error: stat /var/lib/snapd/seed/seed.yaml: no such file or directory
May 20 14:15:33 ubuntu systemd[1]: snapd.snap-repair.service: Main process exited, code=exited, status=1/FAILURE
May 20 14:15:33 ubuntu systemd[1]: snapd.snap-repair.service: Failed with result 'exit-code'.
May 20 14:15:33 ubuntu systemd[1]: Failed to start Automatically fetch and run repair assertions.

Paul Larson (pwlars) on 2020-05-20
tags: added: uc20
Changed in snapd:
status: New → Confirmed
importance: Undecided → High
Ian Johnson (anonymouse67) wrote :

Assigned to Samuele as I took a look at the snap repair code and it seems non-trivial what it's doing with the verification of the assertions. I think that snap repair should use similar code to the seed20 stuff, but I don't know and it would take me longer to figure out all the details here.

Changed in snapd:
assignee: nobody → Samuele Pedroni (pedronis)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers