Scenario:
With two VRF importing each other and with routing policy attached to both VRF
to edit the BgpAttr of the routes, each DBEntry notification for route replication
would end up deleting and re-adding back the replicated route and notifying the
secondary route. This would cause an endless route replication loop
Solution:
Search for secondary path while replicating the route, should compare the BgpAttr
with original BgpAttr of the secondary path.
Added test to validate the above fix. i.e. time stamp of the replicated path is
not updated on triggering the notification of the primary route.
Change-Id: I3e6b31e8b36efbc091353e828b4f9dfa809cf5ff
Closes-Bug: #1597687
(cherry picked from commit ca58c3d77f09098cf3e056e93591ed2d0163e942)
Reviewed: https:/ /review. opencontrail. org/21617 github. org/Juniper/ contrail- controller/ commit/ 933d30c7363d7c4 2eb3128f19b6492 c72f3a1fe2
Committed: http://
Submitter: Zuul
Branch: master
commit 933d30c7363d7c4 2eb3128f19b6492 c72f3a1fe2
Author: Prakash Bailkeri <email address hidden>
Date: Fri Jul 1 14:29:02 2016 +0530
Prevent route replication loop
Scenario:
With two VRF importing each other and with routing policy attached to both VRF
to edit the BgpAttr of the routes, each DBEntry notification for route replication
would end up deleting and re-adding back the replicated route and notifying the
secondary route. This would cause an endless route replication loop
Solution:
Search for secondary path while replicating the route, should compare the BgpAttr
with original BgpAttr of the secondary path.
Added test to validate the above fix. i.e. time stamp of the replicated path is
not updated on triggering the notification of the primary route.
Change-Id: I3e6b31e8b36efb c091353e828b4f9 dfa809cf5ff cf3e056e93591ed 2d0163e942)
Closes-Bug: #1597687
(cherry picked from commit ca58c3d77f09098