When using baremetal driver, genericswitch needs to be listed first

Bug #1945705 reported by Michael Quiniola
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Networking ML2 Generic Switch

Bug Description

Was having issues rebuilding my cluster when I could not get neutron to adjust the switch port vlans properly EXCEPT when deleting the baremetal instance. I discovered this post:


which explained an issue where the user needed "genericswitch" to be listed before "baremetal" in the ml2_conf.ini

By changing the configuration from:

mechanism_drivers = openvswitch,l2population,baremetal,genericswitch


mechanism_drivers = openvswitch,l2population,genericswitch,baremetal

it allowed neutron to properly configure switch ports upon provisioning and moving the port to the proper tenant network.

This isnt necessarily a bug in the neutron code, but needs to be a big red "BE AWARE" notice when configuring either baremetal networking AND the Generic Switch driver.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.