Must bubble up exceptions when Cisco Nexus ML2 Replay enabled
Bug #1481859 reported by
Carol Bouchard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-cisco |
Fix Released
|
Undecided
|
Carol Bouchard | ||
Kilo |
Fix Committed
|
Undecided
|
Carol Bouchard | ||
Liberty |
Fix Released
|
Undecided
|
Carol Bouchard |
Bug Description
The original 'switch replay' plan to have all config entries learned in ML2 drivers when an exception was detected. It would be the responsibility of the Nexus replay code to replay them and not the higher layer. Due to re-evaluation of the replay code, we've since changed direction and will change the code to allow exceptions to bubble up when replay is enabled.
Changed in networking-cisco: | |
assignee: | nobody → Carol Bouchard (caboucha) |
milestone: | none → 1.1.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/219732 /git.openstack. org/cgit/ openstack/ networking- cisco/commit/ ?id=6b86a859db5 fcf931df263b01e 3bf1bd68f0797f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6b86a859db5fcf9 31df263b01e3bf1 bd68f0797f
Author: Carol Bouchard <email address hidden>
Date: Wed Sep 2 11:10:42 2015 -0400
Bubble up exceptions when Nexus replay enabled
There are several changes made surrounding this bug.
1) When replay is enabled, we should bubble exceptions update/ delete post_commit
transactions. This was suppressed earlier by
for received port create/
1422738.
2) When an exception is encountered during a
post_commit transaction, the driver will no longer
mark the switch state to inactive to force a replay.
This is no longer needed since 1481856 was introduced.
So from this point on, only the replay thread will
determine the state of the connection to the switch.
3) In addition to accommodating 1 & 2 above, more detail
data verification was added to the test code.
Change-Id: I97e4de2d5f5652 2eb0212cef4f804 aa4a83957ec
Closes-bug: #1481859