Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix race condition in BGPaaS peering creation - take 2
If the internal ifmap configuration object for the routing-instance for the bgp-routers that comprise a bgp-peering does not exist when processing the bgp-peering, the ifmap config manager does create the internal ifmap configuration object for the bgp-peering. This causes the control node to not create the internal ifmap config object for some bgp-peerings when the control node gets restarted in a scaled bgpaas configuration. This happens for bgp-peerings which get processed before the corresponding routing-instance has been processed. The previous fix did not cover the case where the notification for a routing-instance has not been processed when the notification for the instance-bgp-router link is processed. Fix this by modifying dependency tracker policy to re-evaluate all of the bgp-routers for a routing-instance when processing a notification for the routing-instance itself. This in turn causes a re-evaluation of all the bgp-peerings for those bgp-routers. Change-Id: Idc4425c87037aac1eb96f23394bfae536c17546c Closes-Bug: 1662678
- Loading branch information
Nischal Sheth
committed
Feb 26, 2017
1 parent
775dd7d
commit c2e6857
Showing
2 changed files
with
20 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters