We have the 2.32 release coming very hot, with several important changes that we want to land soon. If you have a chance, please test this release out.
For that if you are in a distribution that is able to re-execute snapd from core (Ubuntu is one of them), just refresh the core snap from the beta channel:
$ sudo snap refresh --channel=beta core
Then let us know if you have any issues in the coming days.
$ sudo snap refresh --channel=beta core
2018/03/27 14:30:27.014868 cmd.go:212: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
2018-03-27T14:30:41Z ERROR skipping security profiles setup for snap "freechessclub" when handling snap "core": no state entry for key
2018-03-27T14:30:42Z ERROR skipping security profiles setup for snap "riot-web" when handling snap "core": no state entry for key
2018-03-27T14:31:01Z ERROR skipping security profiles setup for snap "freechessclub" when handling snap "core": no state entry for key
2018-03-27T14:31:02Z ERROR skipping security profiles setup for snap "riot-web" when handling snap "core": no state entry for key
core (beta) 16-2.32.1 from 'canonical' refreshed
This error message could use some tweaking. As written I have no idea what it means.
Hmmm, looks like a bad blast from the past. I donāt know what the issue is yet. @evan can you share some more information with us, perhaps a copy of your state.json (in private).
$ sudo snap refresh --channel=beta core
2018-03-27T09:49:06-05:00 ERROR skipping security profiles setup for snap
"dotnet-sdk" when handling snap "core": no state entry for key
2018-03-27T09:49:14-05:00 INFO Waiting for restart...
2018-03-27T09:49:33-05:00 ERROR skipping security profiles setup for snap
"dotnet-sdk" when handling snap "core": no state entry for key
core (beta) 16-2.32.1 from 'canonical' refreshed
Ok, so first diagnosis based on Jamieās state: the problem is we have stray connections for a removed snap in the state; these were auto-connections from the snap to core, so we consider that snap affected by core upgrade. Now i need to find out why we didnāt remove these connections when snap was removed.
Followup to my earlier diagnosis (stray connections, see above).
Our snap removal code looks good, connections are discarded from the state as they should (I also verified that by removing some snaps with connections on stable, then refreshing to beta and couldnāt reproduce).
The only explanation I can think of right now is that one of the tasks executed as part of snap removal failed in the past, so we didnāt execute ādiscard-connsā task, and since we donāt have undo for snap remove failures, the snap was gone with connections still in the state. Itās impossible to tell what failed as there is no evidence of that anymore in the state. And itās curious why we didnāt see that error message beforeā¦
I think we didnāt see the error before with older versions of snapd, because the change that makes these stray connections āsurfaceā was made in January: reloadConnections code doesnāt reject such bad connections now, it logs a āNoticeā and the connections are still considered further in the code (leading to the above error).