Containers don't restart after clean host shutdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxd (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug Description
LXD is supposed to record the containers state on host shutdown and restore them to their previous state on restart.
A change in LXD 2.6.2 and LXD 2.0.8 regressed this, so now containers need to be manually started after reboot.
Upstream bug report: https:/
Upstream fix: https:/
This will need to be SRUed very quickly.
# SRU paperwork
## Rationale
Regresses "lxd shutdown".
## Test case
- lxc launch ubuntu:16.04 abc
- lxd shutdown
- ps aux | grep -q abc && echo "FAIL, container still running"
- lxc finger
- lxc list | grep abc | grep RUNNING
## Regression potential
Fix is pretty straightforward and specific to this issue. A test was also added as part of this, so it's very unlikely that anything else would be affected by this fix.
Changed in lxd (Ubuntu Trusty): | |
status: | New → In Progress |
Changed in lxd (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in lxd (Ubuntu Trusty): | |
importance: | Undecided → High |
tags: |
added: verification-done removed: verification-needed |
Changed in lxd (Ubuntu Trusty): | |
status: | In Progress → Fix Released |
Hello Stéphane, or anyone else affected,
Accepted lxd into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ lxd/2.0. 8-0ubuntu1~ ubuntu16. 04.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!