Comment 15 for bug 1662678

Reviewed: https://review.opencontrail.org/28671
Committed: http://github.org/Juniper/contrail-controller/commit/73c20ca36395a3e3287c5f245216d6f7d3373c03
Submitter: Zuul (<email address hidden>)
Branch: R3.0.3.x

commit 73c20ca36395a3e3287c5f245216d6f7d3373c03
Author: Nischal Sheth <email address hidden>
Date: Wed Feb 8 21:05:10 2017 -0800

Fix race condition in BGPaaS peering creation

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.

Fix this by modifying dependency tracker policy to re-evaluate all of
the bgp-peerings for a bgp-router when processing a notification for
the instance-bgp-router edge on the bgp-router.

Change-Id: Id74dda2573491dd7d8df8d9c09d881dc6aa0e95c
Closes-Bug: 1662678