I’m getting a bunch of this error in my boot logs on initial boot with my Core18 image, and it seems to be affecting the Snap Daemon’s ability to run.
Jun 11 13:37:22 localhost snapd: helpers.go:961: cannot retrieve info for snap "kernel": cannot find installed snap "kernel" at revision unset: missing file /snap/kernel/unset/meta/snap.yaml
Surrounding this error are messages from snapd starting and stopping over and over. I will say that my kernel snapcraft.yaml file is perhaps not in the right place, since it’s placed at /snap/snapcraft.yaml. Should the snapcraft.yaml file be placed in the root of the kernel directory? Additionally, I believe that unset is referring to the revision? How do I give it a revision?
well, either something is wrong with your kernel snap (missing meta/snap.yaml (whch is generated from snapcraft.yaml during build)) or you did not properly specify the path in the --snap commandline option for ubuntu-image when building the image (unless you have a brand store i assume your kernel is locally ?)
This is the issue for sure then. A kernel snap and all snaps by definition need to have snap.yaml. This should have been generated for you by snapcraft if you are using snapcraft to build the kernel snap.
Unfortunately, it’s confidential. I can say that it came from a Core16 build that seemed to work pretty well, though I don’t know if the error in question happened on that one. Also, I bumped the kernel version from 4.14 to 4.19 and then 5.4.
A shot in the dark I was thinking of, though, is there a reason anyone can think of off the top of their head that the image is expecting the snap.yaml file at unset/meta/snap.yaml instead of… well, anywhere else?
thats your prob … there should be a version (for properly released snaps it is the store revision. for sideloaded snaps (ie. via using the --snap option in ubuntu-image or from cmdline via --dangerous when installing an app snap) a revision number of xN is genereated at snap install time (N being an iterative number) somehow you did not get this generated revision number and something falls back to “unset” …