Neutron: Nexus switch missing configuration after VMs creation/deletion
Bug #1407801 reported by
Danny Choi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-cisco |
Fix Committed
|
Undecided
|
Rich Curran | ||
Bug Description
Nexus switch missing VLAN configurations after VMs create/delete.
Revision history for this message
| Danny Choi (dannchoi) wrote | #1 |
| affects: | python-neutronclient → networking-cisco |
| Changed in networking-cisco: | |
| status: | New → Fix Committed |
| assignee: | nobody → Rich Curran (rcurran) |
| tags: |
added: nexus removed: cisco |
Revision history for this message
| Rich Curran (rcurran) wrote | #2 |
To post a comment you must log in.
Rich Curran has committed a fix for this:
commit 8c01b26e770ff2c
Author: Rich Curran <email address hidden>
Date: Thu Jan 22 12:18:58 2015 -0500
Single threading required for ML2 cisco/nexus driver
During multi-VM creation (creates neutron ports) debug indicates that
multiple threads are used in calls to the update and delete (on removing
the VMs) methods. Since database access is used in the cisco nexus MD
event methods for determining the current switch configuration, failures
are seen (on both updates and deletes) on programming the nexus switch.
This commit forces single threaded access to these methods.
Change-Id: I275d1a8e43d69c