group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1647312@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lxd - 2.6.2-0ubuntu3

---------------
lxd (2.6.2-0ubuntu3) zesty; urgency=medium

  * Fix container last-state recording (LP: #1647312)
    - 0001-Fix-container-state-recording.patch
    - 0002-tests-Test-lxd-shutdown.patch
    - 0003-Only-mark-ready-once-containers-are-up.patch

 -- Stéphane Graber <stgraber@xxxxxxxxxx>  Mon, 05 Dec 2016 13:33:41
+0100

** Changed in: lxd (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647312

Title:
  Containers don't restart after clean host shutdown

Status in lxd package in Ubuntu:
  Fix Released
Status in lxd source package in Trusty:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released

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://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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1647312/+subscriptions