yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

** Changed in: nova
    Milestone: None => havana-2

-- 
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/1177811

Title:
  Resize STOPPED instance on same host is in ACTIVE state after resize

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Testing on stable/grizzly, if you have an instance in STOPPED state
  and then resize it to the same host, the resized instance is in ACTIVE
  state even though it's still powered off in the hypervisor.

  The resize/migrate operations allow starting from STOPPED or ACTIVE
  state:

  https://github.com/openstack/nova/blob/stable/grizzly/nova/compute/api.py#L1951

  However, when the resize is confirmed, it updates the instance to
  ACTIVE state (even though it was originally in STOPPED state):

  https://github.com/openstack/nova/blob/stable/grizzly/nova/compute/api.py#L1862

  Eventually the power states are synched between the database and the
  hypervisor and the instance is set back to STOPPED state:

  https://github.com/openstack/nova/blob/stable/grizzly/nova/compute/manager.py#L3680

  But the code should be keeping track of the original state of the
  instance before the resize and make sure it's in that state once the
  operation is verified.

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