yahoo-eng-team team mailing list archive

[Alan Pevec <1198284@xxxxxxxxxxxxxxxxxx>]

** 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/1198284

Title:
  hypervisor_hostname not updated on evacuate

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

Bug description:
  On master havana, using KVM/libvirt driver, found a problem where the
  hypervisor_hostname property isn't updated on the instance after it's
  evacuated (note that the host property is updated).

  Looking at existing bugs, bug 1081355 looks to be in the same theme
  but it's not the same issue.

  Steps are:

  1. Boot instance on node A with flavor 3.
  2. Resize instance (migrate) with flavor 4 (no target node is specified, it goes to node B).
  3. Confirm the resize.
  4. Bring down node B.
  5. Evacuate the instance to node C.
  6. Resize instance (mirate) with flavor 5.
  7. Confirm the resize - at this point it blows up because it's trying to get the resource tracker for node B which is down.

  Looking at the evacuate code in compute manager, the host is updated
  by hypervisor_hostname is not:

  https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1733

  Attached a more detailed set of steps with 'nova show' output between
  each step.

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