Removing when an app is running results in a half removal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
High
|
Unassigned | ||
snapd (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug Description
|-- sergiusens@
$ sudo snap remove telegram
[sudo] password for sergiusens:
[\] Remove snap "telegram" from the system
error: cannot perform the following tasks:
- Remove snap "telegram" from the system (remove /snap/telegram/
|-- sergiusens@
$ sudo snap remove telegram
[|] Remove security profile for snap "telegram"
error: cannot perform the following tasks:
- Remove snap "telegram" from the system (remove /snap/telegram/
I had an apps/telegram/
Changed in snapd (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in snappy: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → sru-1 |
Changed in snappy: | |
status: | Triaged → Fix Committed |
Changed in snapd (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in snapd (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
Changed in snappy: | |
status: | Fix Committed → Fix Released |
so the question is why we don't fail unmounting/don't get an error at unmount time;
either way we need to reason a bit how undo/bailout should look like if we fail early enough (right now there's no undo support in remove handling)