Make BGPaaS port change processing more defensive
Bug #1669871 reported by
Nischal Sheth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
Medium
|
Nischal Sheth | |||
R3.1 |
Fix Committed
|
Medium
|
Nischal Sheth | |||
R3.2 |
Fix Committed
|
Medium
|
Nischal Sheth | |||
Trunk |
Fix Committed
|
Medium
|
Nischal Sheth |
Bug Description
Consider the following scenario:
Peer1 has source port p1
Peer2 has source port p2
Configuration for Peer1 is changed to have port p2 i.e. both Peer1 and
Peer2 have port p2. Existing implementation removes Peer2 from it's port
to peer mapping table under the assumption that the port for Peer2 will
soon change to a new value. However, if the port for Peer1 is now changed
back to p1, the port to peer mapping table no longer has an entry that
maps p2 to Peer2.
Review in progress for https:/ /review. opencontrail. org/29312
Submitter: Nischal Sheth (<email address hidden>)