Failed evacuations leave neutron ports on destination host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Jack Ding |
Bug Description
Description
===========
This is related to https:/
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_
* 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
Changed in nova: | |
assignee: | nobody → Jack Ding (jackding) |
status: | Opinion → In Progress |
Evacuate behavior changes are so dicey at this point that I think anything like this probably needs a spec to actually think through the edge conditions.
Please dive in here if you are interested - https:/ /specs. openstack. org/openstack/ nova-specs/ readme. html