Cannot safely refresh from edge to stable with ubuntu-core
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
High
|
Unassigned | ||
Bug Description
It's possible to wedge your system by switching the ubuntu-core snap from edge to stable snap:
$ sudo snap refresh --channel=edge ubuntu-core
74.70 MB / 74.70 MB [======
ubuntu-core (edge) 16.04.1 from 'canonical' upgraded
$ sudo snap refresh ubuntu-core --channel=stable
error: cannot communicate with server: Get http://
$ journalctl -xe
-- The start-up result is done.
Sep 30 14:01:15 elsa /usr/lib/
Sep 30 14:01:15 elsa snapd[13610]: error: cannot downgrade: snapd is too old for the current system state (patch level 4)
Sep 30 14:01:15 elsa systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
Sep 30 14:01:15 elsa systemd[1]: snapd.service: Unit entered failed state.
Sep 30 14:01:15 elsa systemd[1]: snapd.service: Failed with result 'exit-code'.
Sep 30 14:01:16 elsa systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
Sep 30 14:01:16 elsa systemd[1]: Stopped Snappy daemon.
-- Subject: Unit snapd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://
--
-- Unit snapd.service has finished shutting down.
Sep 30 14:01:16 elsa systemd[1]: snapd.service: Start request repeated too quickly.
Sep 30 14:01:16 elsa systemd[1]: Failed to start Snappy daemon.
-- Subject: Unit snapd.service has failed
-- Defined-By: systemd
-- Support: http://
--
-- Unit snapd.service has failed.
--
-- The result is failed.
| Changed in snappy: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: eco-team |
| Michael Vogt (mvo) wrote | #1 |
| affects: | snappy → snapd |
This should actually be mostly ok now. Only if you have a really old local ubuntu-core snap and revert to it things will break. But stable/edge should be fine nowdays.