neutron doesnt delete port binding level when deleting an inactive port binding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Adrian Chiris |
Bug Description
When performing VM live migration with a normal port (OVS mechanism driver) nova creates an in-active binding on the destination node then activates that binding upon successful migration.
in case of failure to migrate with libvirt, an exception is raised, nova performs a rollback operation for the live migration and instance remains in running state on the source node.
part of the rollback operation is deleting neutron's port binding on the destination node with the following API call:
DELETE /v2.0/ports/
this call, for an inactive port binding (which was never activated), does not delete the port's binding level which causes future migration attempts to fail.
Reproduction setup:
- devstack deployment of an all in one and a compute node from master
- OS: FC28
- QEMU hypervisor
- neutron OVS mechanism driver enabled
- perform further configurations to enable live-migration : https:/
- block libvirt migration port with iptables on destination node (on my setup i just needed to activate iptables on destination node)
reproduction steps:
http://
Changed in neutron: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
status: | Confirmed → In Progress |
assignee: | nobody → Adrian Chiris (adrian.chiris) |
the following patch proposes a fix to the issue:
https:/ /review. openstack. org/#/c/ 634276/