neutron bridge name is not always set for ml2/ovs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Slawek Kaplonski |
Bug Description
* Summary: neutron bridge name is not always set for ml2/ovs
* High level description: to enable live migration between different ml2
drivers utilizing multiple port bindings nova cannot assume the bridge name of
the destination host when generating the vm domain(e.g. libvirt xml)
to this end the ovs bridge name which is set when using trunk ports
also needs to be set in the general case.
* Expected output:
when a port is bound by the ml2/ovs mech driver the bridge
name is set in the vif binding-details.
* Actual output:
because the bridge name is not in the general case when you live migrate
from linux bridge to ovs the vm is attach to a new ovs bridge using the linux
bridge, bride name of the source node node instead attaching the vm interface
to the br-int bridge. as a result while the migration is successful
the vm will have no network connectivity as this new bridge is not connect to the
br-int via a patch port pair.
* Version:
** OpenStack version master/Rocky RC1
** Centos 7.5
** DevStack
* Environment: multinode default devstack install.
* Perceived severity: low( it is a trival fix but it does prevent migrating form lb to ovs hosts)
Click on extra options for the following:
Changed in neutron: | |
assignee: | nobody → sean mooney (sean-k-mooney) |
Changed in neutron: | |
importance: | Undecided → Wishlist |
tags: | removed: rfe |
tags: | removed: rfe-triaged |
Changed in neutron: | |
assignee: | sean mooney (sean-k-mooney) → Slawek Kaplonski (slaweq) |
Confirmed that this bug is reproducible on master. Boot a VM in a linuxbridge node, migrate the VM to an OVS node, the VM will lose network connectivity.