Installing core snap in container often fails

Bug #1716923 reported by Michał Sawicz
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
High
Cris Dywan

Bug Description

Very often, when trying to build a snap with SNAPCRAFT_CONTAINER_BUILDS=1, the build fails to install the core snap:

Looking up assertion ['account-key', 'public-key-sha3-384=BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul']
Looking up assertion ['snap-declaration', 'snap-name=core']
Looking up assertion ['snap-revision', 'snap-revision=2844', 'snap-id=99T7MUlRhtI3U0QFgl5mXXESAiSwt776']
Adding assertion core_2844.assert
Installing /run/core_2844.snap
error: cannot perform the following tasks:
- Copy snap "core" data (cannot copy "/var/snap/core/2844" to "/var/snap/core/2844": failed to copy all: "cp: cannot stat '/var/snap/core/2844': No such file or directory" (1))

It seems to be trying to refresh to the same core revision that already exists?

Revision history for this message
John Lenton (chipaca) wrote :

there was a bug in snapd,
https://forum.snapcraft.io/t/cant-re-install-existing-snap/1824/9
which has been fixed but not yet released to stable; it should be in 2.28.
There's also a minor bug in snapcraft that triggers it, see
https://forum.snapcraft.io/t/snapcraft-container-builds-triggering-a-bug-in-snapd/1990

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

I will mark this as invalid given that this is a snapd bug. That said, we are moving to only installing the core snap if the version has changed so will set it to triaged instead and repurpose the bug for that task.

Changed in snapcraft:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Christian Dywan (kalikiana)
milestone: none → 2.35
Revision history for this message
Cris Dywan (kalikiana) wrote :
Changed in snapcraft:
status: Triaged → In Progress
Cris Dywan (kalikiana)
Changed in snapcraft:
status: In Progress → Fix Committed
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.