snapd enters fail state after corrupted snap.yaml (probably)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
High
|
John Lenton |
Bug Description
classic system: Ubuntu server 16.04.1
snap version:
snap 2.34.2+
Core edge channel, revision: 5104
While developing snap and combining use of 'snap try' and editing of snap.yaml I have managed to crash snapd to the point it won't restart
log from journalctl for snapd.service suggests there is indeed some yaml parsing panic.
https:/
If this is the case it should sure not derail snapd to the point it cannot recover....
Manually un mounting trubled snap from /snap/<
removed crash, so snapd service can start again.
Next attempt to 'snap try' will immediately crash snapd and service enters fail state as before, validating it's snap.yaml issue
snap.yaml causing the trouble:
https:/
Changed in snapd: | |
status: | In Progress → Fix Committed |
Changed in snapd: | |
status: | Fix Committed → Fix Released |
corruption in snap.yaml is caused by two identical item in environment section.
Seems like service fail state is related to snap try, when snap.yaml is edited, but snapd has no clear way to refuse it, as it has been already installed as previous revision with snap try
When doing clean install, snap is refused and snapd service recovers