As described in DE588,
"With neutron multiworkers configured, there is a potential race condition
issue where some of the VLANs will not be configured on one or more N9k
switches.
Fix is to allow the vlan create command to be sent down to a switch
under most event conditions. Long term fix will be to introduce a new
column in the port binding DB table that indicates the true state of the
entry/row.
Closes-Bug: #1491940
Change-Id: If1da1fcf16a450c1a4107da9970b18fc64936896
(cherry picked from commit 0e48a16e77fc5ec5fd485a85f97f3650126fb6fe)
Reviewed: https:/ /review. openstack. org/221472 /git.openstack. org/cgit/ openstack/ networking- cisco/commit/ ?id=f08fb31f20c 2d8cc1e6b71784c dfd9604895e16d
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit f08fb31f20c2d8c c1e6b71784cdfd9 604895e16d
Author: Rich Curran <email address hidden>
Date: Thu Sep 3 13:23:52 2015 -0400
ML2 cisco_nexus MD: VLAN not created on switch
As described in DE588,
"With neutron multiworkers configured, there is a potential race condition
issue where some of the VLANs will not be configured on one or more N9k
switches.
/etc/ neutron/ neutron. conf ------- ------- ------- -
---
api_workers=3
rpc_workers=3"
Fix is to allow the vlan create command to be sent down to a switch
under most event conditions. Long term fix will be to introduce a new
column in the port binding DB table that indicates the true state of the
entry/row.
Closes-Bug: #1491940 c1a4107da9970b1 8fc64936896 5fd485a85f97f36 50126fb6fe)
Change-Id: If1da1fcf16a450
(cherry picked from commit 0e48a16e77fc5ec