Cisco nexus plugin fails to create vlan on a previously used switch

Bug #1223402 reported by Ralf Haferkamp
10
This bug affects 2 people
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:

QuantumClientException: Failed to configure Nexus:
 <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
        <configure>
          <__XML__MODE__exec_configure>
            <vlan>
              <vlan-id-create-delete>
                <__XML__PARAM_value>582</__XML__PARAM_value>
                <__XML__MODE_vlan>
                  <name>
                    <vlan-name>q-582</vlan-name>
                  </name>
                </__XML__MODE_vlan>
              </vlan-id-create-delete>
            </vlan>
          </__XML__MODE__exec_configure>
        </configure>
      </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: nexus cisco
Henry Gessau (gessau)
tags: added: cisco
Revision history for this message
Henry Gessau (gessau) wrote :

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.

Revision history for this message
Aaron Rosen (arosen) wrote :

Out of curiosity why does neutron need to on demand program vlans on the switche(s). Why not as part of setup have the admin trunk a range of vlans they want to use and tell neturon about that. That seems like it would simplify things greatly?

Changed in neutron:
status: New → Triaged
Revision history for this message
Sam Betts (sambetts) wrote :

Does this need moving over to the networking-cisco vendor repo bug tracker, if its still a valid issue?

no longer affects: neutron
Henry Gessau (gessau)
tags: added: nexus
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.