Cisco nexus plugin fails to create vlan on a previously used switch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-cisco |
New
|
Undecided
|
Unassigned |
Bug Description
When reconfiguring quantum from scratch with a cisco nexus switch that was previously used in a quantum setup, creating a VLAN might fail with:
QuantumClientEx
<config xmlns:xc=
<configure>
<vlan>
</vlan>
</config>
. Reason: ERROR: VLAN with the same name exists
The workaround for this is pretty easy. Just delete (even renaming seems to be enough) all the vlans that quantum is supposed to manage on the switch using the configuration console.
But couldn't the nexus plugin also simply overwrite the exisiting VLAN in case it already exists on the switch but not it the database?
tags: | added: cisco |
Changed in neutron: | |
status: | New → Triaged |
no longer affects: | neutron |
tags: | added: nexus |
I am uncomfortable with changing the existing behavior. A pre-existing VLAN on the switch may have been set up by another admin who does not want neutron to overwrite it.
Instead, we could add a new configuration option, say "clear_ vlans_on_ init", which would cause neutron to clear any existing unused VLANs from the tenant VLAN range at startup.