yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1182056] Re: Failed VM's not set to error state on exception

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Alan Pevec <1182056@xxxxxxxxxxxxxxxxxx>
Date: Thu, 08 Aug 2013 19:52:35 -0000
Reply-to: Bug 1182056 <1182056@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova/grizzly
       Status: Fix Committed => 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/1182056

Title:
  Failed VM's not set to error state on exception

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  Fix Released

Bug description:
  We've identified that when an instance build fails because it has
  exceeded the number of retries (i.e. been tried on 3 different hosts)
  the upstream logic in the scheduler does not correctly set the VM
  state to ERROR.

  There is an exception handler for NoValidHost in
  manager.run_instance(), but it relies on request_spec[instance_uuids]
  to determine which instances to put into the Error State, and
  schedule_run_instance removes this value (as its normally about to
  split the request up into several separate requests).

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