ML2 Cisco Nexus MD: VLAN/trunk config not created on all switches

Bug #1512463 reported by Rich Curran
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-cisco
Fix Committed
Undecided
Rich Curran
Kilo
Fix Committed
Undecided
Rich Curran
Liberty
Fix Committed
Undecided
Rich Curran

Bug Description

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.

Tags: ml2 nexus cisco
Rich Curran (rcurran)
Changed in networking-cisco:
assignee: nobody → Rich Curran (rcurran)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-cisco (master)

Fix proposed to branch: master
Review: https://review.openstack.org/241216

Changed in networking-cisco:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-cisco (master)

Reviewed: https://review.openstack.org/241216
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=8e7017c8ba6c0d5cc5ef6f250c4a572556fd70a4
Submitter: Jenkins
Branch: master

commit 8e7017c8ba6c0d5cc5ef6f250c4a572556fd70a4
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:
    - 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.

    Change-Id: I3bc5456282cda3c1916327ef876d2fcd3e3cbeb8
    Closes-Bug: #1512463

Changed in networking-cisco:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-cisco (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/241760

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on networking-cisco (stable/kilo)

Change abandoned by rcurran (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/241747
Reason: bad cherry-pick

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-cisco (stable/kilo)

Reviewed: https://review.openstack.org/241760
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=db24e3d3687c3dec84f39406fecf1635610251ff
Submitter: Jenkins
Branch: stable/kilo

commit db24e3d3687c3dec84f39406fecf1635610251ff
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:
    - 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.

    Change-Id: I3bc5456282cda3c1916327ef876d2fcd3e3cbeb8
    Closes-Bug: #1512463
    (cherry picked from commit 8e7017c8ba6c0d5cc5ef6f250c4a572556fd70a4)

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.