Reviewed: https://review.openstack.org/155120 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a9e4e2c9a5aaa4d675057790816aa395bc27e9bc Submitter: Jenkins Branch: master
commit a9e4e2c9a5aaa4d675057790816aa395bc27e9bc Author: George Shuklin <[email protected]> Date: Fri May 1 17:57:00 2015 +0300 If rescue failed set instance to ERROR The compute API will allow attempting to rescue an instance that is in active/stopped/error state. The compute manager will power off the instance before calling driver.rescue. If the rescue call fails in the virt driver, we should set the instance to ERROR state since we (1) know the instance is definitely not active since the compute manager powered it off and (2) we don't know what failed in the virt driver, so punting and putting the instance into ERROR state is better than leaving it broken and not signaling that with the vm_state. Co-Authored-By: Matt Riedemann <[email protected]> Closes-Bug: 1418590 Change-Id: Ia1054d3f9193f876803f8b5a26d00bd9d5d66c12 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418590 Title: Instance is left in ACTIVE state even if rescue fails To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1418590/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
