Refreshing core in edge waiting on "...security profiles (phase 2)"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On stable, I can `snap refresh core` and it will exit after having scheduled a reboot, so the user can reboot themselves to speed the process up.
On edge, refreshing core schedules a reboot, but then the command stays on "Setup snap "core" (...) security profiles (phase 2)" with the throbber going back and forth, it's unclear what can the user do. Would Ctrl+C interrupt the upgrade? Do I have to wait for the reboot?
====
saviq@localhost:~$ snap refresh core
Setup snap "core" (5490) security profiles
Broadcast message from <email address hidden> (Thu 2018-09-13 18:48:13 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Thu 2018-09-13 18:58:13 UTC!
2018-09-
2018-09-
2018-09-
2018-09-
Setup snap "core" (5490) security profiles (phase 2)
Broadcast message from <email address hidden> (Thu 2018-09-13 18:48:30 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Thu 2018-09-13 18:58:30 UTC!
2018-09-
Setup snap "core" (5490) security profiles (phase 2)
Broadcast message from <email address hidden> (Thu 2018-09-13 18:49:30 UTC):
reboot scheduled to update the system - temporarily cancel with 'sudo shutdown -c'
The system is going down for reboot at Thu 2018-09-13 18:58:30 UTC!
Setup snap "core" (5490) security profiles (phase 2)
Changed in snapd: | |
status: | Fix Committed → Fix Released |
We reworked the way to present this and `snap refresh core` does no longer hang in this strange state.