yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1226352] Re: seemingly inconsistent use of _set_instance_error_state in nova/compute/manager.py

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Melanie Witt <1226352@xxxxxxxxxxxxxxxxxx>
Date: Tue, 08 Oct 2013 22:14:05 -0000
Reply-to: Bug 1226352 <1226352@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

It looks like this was fixed by https://review.openstack.org/32214.

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1226352

Title:
  seemingly inconsistent use of _set_instance_error_state in
  nova/compute/manager.py

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  versions: essex (2012.1) and grizzly (2013.1)

  The use of "_set_instance_error_state" function seems to be
  inconsistent in nova/compute/manager.py. For example, when a "nova
  boot" command fails, the VM may end in ERROR state due to the use of
  "_set_instance_error_state". If a "nova reboot" fails, however,
  "_set_instance_error_state" is not called and VM will not be set to
  ERROR.

  We think that the VM should be set to ERROR in both cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1226352/+subscriptions