Hello,
On raspberry-pi3 this works silently in the background when a new core version comes out.
But when forced to refresh from a terminal via ssh this gives that:
Before refresh:
denisnone@rpic:~$ snap info core
name: core
summary: "snapd runtime environment"
publisher: canonical
contact: snappy-canonical-storeaccount@canonical.com
description: |
The core runtime environment for snapd
type: core
tracking: edge
installed: 16-2 (1637) 70MB -
refreshed: 2017-04-06 04:23:48 +0000 UTC
channels:
stable: 16-2 (1580) 69MB -
candidate: 16-2 (1690) 70MB -
beta: 16-2 (1805) 71MB -
edge: 16-2 (1823) 70MB -
Refresh process:
denisnone@rpic:~$ snap refresh core --candidate
[/] Download snap "core" (1690) from channel "candidate"
Broadcast message from root@rpic (Mon 2017-05-01 16:10:00 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:20:00 UTC!
core 45.84 MB / 67.47 MB [=====================================================================>---------------------------------] 67.95% 792.48 KB/s 27s
Broadcast message from root@rpic (Mon 2017-05-01 16:11:00 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:20:00 UTC!
[\] Mount snap "core" (1690)
Broadcast message from root@rpic (Mon 2017-05-01 16:12:00 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:20:00 UTC!
[/] Make snap "core" (1690) available to the system
Broadcast message from root@rpic (Mon 2017-05-01 16:12:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
2017-05-01T16:12:06Z INFO Waiting for restart...
[-] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:13:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[\] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:14:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[|] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:15:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[/] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:16:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
2017-05-01T16:16:45Z INFO Waiting for restart...
[-] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:17:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[\] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:18:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[|] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:19:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[/] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:20:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
[-] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:21:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Mon 2017-05-01 16:22:06 UTC!
2017-05-01T16:21:45Z INFO Waiting for restart...
[\] Setup snap "core" (1690) security profiles (phase 2)
Broadcast message from root@rpic (Mon 2017-05-01 16:22:06 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot NOW!
Connection to rpic.local closed by remote host.
Connection to rpic.local closed.
After reboot
denisnone@rpic:~$ snap info core
name: core
summary: "snapd runtime environment"
publisher: canonical
contact: snappy-canonical-storeaccount@canonical.com
description: |
The core runtime environment for snapd
type: core
tracking: candidate
installed: 16-2 (1690) 70MB -
refreshed: 2017-04-11 12:29:57 +0000 UTC
channels:
stable: 16-2 (1580) 69MB -
candidate: 16-2 (1690) 70MB -
beta: 16-2 (1805) 71MB -
edge: 16-2 (1823) 70MB -
denisnone@rpic:~$
Changes info:
denisnone@rpic:~$ snap changes
ID Status Spawn Ready Summary
19 Done 2017-05-01T16:09:54Z 2017-03-14T20:19:03Z Refresh "core" snap from "candidate" channel
20 Done 2017-05-01T16:09:56Z 2017-05-01T16:10:26Z
denisnone@rpic:~$ snap change 19
Status Spawn Ready Summary
Done 2017-05-01T16:09:54Z 2017-05-01T16:11:26Z Download snap "core" (1690) from channel "candidate"
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:00Z Fetch and check assertions for snap "core" (1690)
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:03Z Mount snap "core" (1690)
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:03Z Stop snap "core" services
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:03Z Remove aliases for snap "core"
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:04Z Make current revision for snap "core" unavailable
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:04Z Copy snap "core" data
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:05Z Setup snap "core" (1690) security profiles
Done 2017-05-01T16:09:54Z 2017-05-01T16:12:06Z Make snap "core" (1690) available to the system
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:55Z Setup snap "core" (1690) security profiles (phase 2)
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:55Z Set automatic aliases for snap "core"
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:55Z Setup snap "core" aliases
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:55Z Start snap "core" (1690) services
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:56Z Remove data for snap "core" (1580)
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:59Z Remove snap "core" (1580) from the system
Done 2017-05-01T16:09:54Z 2017-03-14T20:18:59Z Clean up "core" (1690) install
Done 2017-05-01T16:09:54Z 2017-03-14T20:19:03Z Run configure hook of "core" snap if present
......................................................................
Make snap "core" (1690) available to the system
2017-05-01T16:12:06Z INFO Requested system restart.
......................................................................
Setup snap "core" (1690) security profiles (phase 2)
2017-05-01T16:12:06Z INFO Waiting for restart...
2017-05-01T16:16:45Z INFO Waiting for restart...
2017-05-01T16:21:45Z INFO Waiting for restart...
denisnone@rpic:~$
So it refreshes well, but it sits in that “security profiles (phase 2)” forever until scheduled reboot hits.
And yes, the image is an Ubuntu official image.
About my board.
Installing/removing snaps works without problems, “hello-world” for example installs well.
Docker snap installs but gives an INFO:
2017-05-01T16:32:11Z INFO cannot auto connect docker:docker-cli to docker:docker-daemon: (slot auto-connection), existing connection state "docker:docker-cli docker:docker-daemon" in the way
docker 1.13.1-0 from 'docker-inca' installed
I will collect journald information and post it shortly after re-flashing my image on sd-card to clean all the mess and start over again.