This was happening in headless mode, where stale walk was fired after few
seconds and because of scale notify walk used to take longer than same.
Stale and notify walk were using same walker. When stale walk was started it
used to cancel notify walker in turn leaving few route entries in not exported
state.
Because of this issue like fmg-bum-tree not built, OVS mac not programmed in
vrouter(resulting in unknown unicast flood), QFX missing from BUM .
Reviewed: https:/ /review. opencontrail. org/32264 github. com/Juniper/ contrail- controller/ commit/ b8bb87016fea60a 4aa0e4e366d06c3 0c3285a1c5
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.1
commit b8bb87016fea60a 4aa0e4e366d06c3 0c3285a1c5
Author: Manish <email address hidden>
Date: Tue May 30 14:36:34 2017 +0530
Few route's export not done from agent to CN.
This was happening in headless mode, where stale walk was fired after few
seconds and because of scale notify walk used to take longer than same.
Stale and notify walk were using same walker. When stale walk was started it
used to cancel notify walker in turn leaving few route entries in not exported
state.
Because of this issue like fmg-bum-tree not built, OVS mac not programmed in
vrouter(resulting in unknown unicast flood), QFX missing from BUM .
Solution:
Seperate both the walks.
Change-Id: I47ca07b0d22aa3 61a36a01ea06df2 eb5c6f628a6
Closes-bug: #1692795