ML2 Cisco Nexus MD: VLAN/trunk config not created on all switches
In the following topology/configuration:
- two nexus switches
- three neutron-server controllers (HA)
- dhcp_agents_per_network=3
- two port-channels being configured per nexus switch
a race condition was observed that caused one switch missing a vlan global
configuration and one of the port-channels not being trunked with the vlan.
The 2nd switch was often not programmed at all.
This fix removes the code that attempts to verify (and then program) if a
vlan/trunk interface was programmed on the switch.
Reviewed: https:/ /review. openstack. org/241216 /git.openstack. org/cgit/ openstack/ networking- cisco/commit/ ?id=8e7017c8ba6 c0d5cc5ef6f250c 4a572556fd70a4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8e7017c8ba6c0d5 cc5ef6f250c4a57 2556fd70a4
Author: Rich Curran <email address hidden>
Date: Tue Nov 3 09:08:54 2015 -0500
ML2 Cisco Nexus MD: VLAN/trunk config not created on all switches
In the following topology/ configuration: per_network= 3
- two nexus switches
- three neutron-server controllers (HA)
- dhcp_agents_
- two port-channels being configured per nexus switch
a race condition was observed that caused one switch missing a vlan global
configuration and one of the port-channels not being trunked with the vlan.
The 2nd switch was often not programmed at all.
This fix removes the code that attempts to verify (and then program) if a
vlan/trunk interface was programmed on the switch.
Change-Id: I3bc5456282cda3 c1916327ef876d2 fcd3e3cbeb8
Closes-Bug: #1512463