yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1166771] Re: Live-migration leaves instance in MIGRATING state if scheduler fails to find a host

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Alan Pevec <1166771@xxxxxxxxxxxxxxxxxx>
Date: Fri, 10 May 2013 00:00:19 -0000
Reply-to: Bug 1166771 <1166771@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/1166771

Title:
  Live-migration leaves instance in MIGRATING state if scheduler fails
  to find a host

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

Bug description:
  This can be easily reproduced on a single devstack install:

  1. Boot an instance and wait for it to become active
  2. Issue live-migration command without setting destination host to trigger scheduler host selection

  Since there is just one compute node in this setup (the source node),
  scheduling will return a NoValidHost exception.

  Expected behavior is for the instance task state to be reset to None,
  while the actual behavior is that it is left as MIGRATING.

  The solution is to add this exception to the list of exceptions for
  which the instance state is reset on a failure.

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