yahoo-eng-team team mailing list archive

[Jack Ding <1659062@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova
     Assignee: (unassigned) => Jack Ding (jackding)

** Changed in: nova
       Status: Opinion => In Progress

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

Title:
  Failed evacuations leave neutron ports on destination host

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===========
  This is related to https://bugs.launchpad.net/nova/+bug/1430042 and the associated fix https://review.openstack.org/#/c/169827/; if an evacuation fails there is no reverting of the neutron ports' host_id binding back to the source host.

  This may or may not be a bug, but if the evacuation fails and the
  source host comes back up and VMs are expected to be running, then the
  neutron ports should probably be rolled back.

  Steps to reproduce
  ==================
  * Raise an exception at some point in the evacuation flow after the setup_instance_network_on_host calls in _do_rebuild_instance in the manager
  * Issue an evacuation of a VM to the host that will fail

  Expected result
  ===============
  * If the evacuation fails the expectation would be to have the neutron ports have their host_id binding updated to be the source host.

  Actual result
  =============
  * The ports host_id bindings remain as the destination host.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
     Newton

  2. Which hypervisor did you use?
     PowerVM

  2. Which storage type did you use?
     N/A

  3. Which networking type did you use?
     Neutron with SEA

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