Defining base snap breaks snapping Subiquity

[Niek Wessels]

Subiquity basically uses an old snapcraft.yaml configuration. I updated this configuration to use base: core18 and multipass and set up all of its dependencies and packages to be local. When injecting the snap into an ISO, snapd gets stuck in "Wait until snapd is fully seeded". Checking back with TTY2, I see that the /snap/bin directory is empty. When not specifying a base keyword, the /snap/bin directory consists of the required snap parts and runs correctly.

[Niek Wessels (nwessels)]

My own snapcraft.yaml

[Niek Wessels (nwessels)]

And ofcourse, the default yaml:

https://github.com/CanonicalLtd/subiquity/blob/master/snapcraft.yaml

[Michael Hudson-Doyle (mwhudson)]

Ah yes, we need to fix this. IIRC, even changing snapcraft.yaml to "base: core" requires some changes to build successfully.

[John Lenton (chipaca)]

I think the reason you see snapd get stuck on boot is because with the updated snap the seed.yaml is no longer valid. Missing or out of order bases, or content interfaces, would typically do this.

'snap debug validate-seed' was added in 2.39, and expanded in 2.41 to report on these issues.

There is not much snapd can _do_ on a system with an invalid seed; it needs checking before creating the system image.

I'm setting snapd's bug task to Invalid, but if there is something snapd needs to do please let us know (set it back to New so our triage picks it up).

Thank you.