Public bug reported: 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://github.com/lxc/lxd/issues/2686 Upstream fix: https://github.com/lxc/lxd/pull/2687 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. ** Affects: lxd (Ubuntu) Importance: High Status: In Progress ** Affects: lxd (Ubuntu Trusty) Importance: High Status: In Progress ** Affects: lxd (Ubuntu Xenial) Importance: High Status: In Progress ** Also affects: lxd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxd (Ubuntu Trusty) Status: New => In Progress ** Changed in: lxd (Ubuntu Xenial) Status: New => In Progress ** Changed in: lxd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: lxd (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647312 Title: Containers don't restart after clean host shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1647312/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
