The NodeTableExport() should call ConfigChanged() for a node-delete.
Bug #1462549 reported by
Tapan Karwa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
Fix Committed
|
Medium
|
Tapan Karwa | |||
R2.1 |
Fix Committed
|
Medium
|
Tapan Karwa | |||
R2.20 |
Fix Committed
|
High
|
Tapan Karwa | |||
Trunk |
Fix Committed
|
Medium
|
Tapan Karwa |
Bug Description
If the node gets revived (add followed by delete followed by add), we could have cases where the CRC in the second add is the same as CRC in the first add, causing 'bool change' to be false. But, the node has really changed since there was a delete in the middle.
no longer affects: | juniperopenstack/r2.30 |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/11329
Submitter: Tapan Karwa (<email address hidden>)