This happens because route table subscribe walk is started without initializing
type of walk. In that case disassociate is issued resulting in unsubscription.
This issue will happen if this walk requests are processed after route
notification in controller. Notification would have done sub but walk will
unsub. If walk finishes before route notification then issue is not seen.
Change-Id: I9a3d02d901a1d9cb4f2755e5c6254231f35f13f7
Closes-bug: #1732394
(cherry picked from commit 236dad449e496649e6c69eafcb1991d4e5f7d957)
Reviewed: https:/ /review. opencontrail. org/37838 github. com/Juniper/ contrail- controller/ commit/ 4ccd1c1bd344a99 d27d5665d109797 d9046dfeff
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 4ccd1c1bd344a99 d27d5665d109797 d9046dfeff
Author: Manish <email address hidden>
Date: Thu Nov 16 12:32:35 2017 +0530
Multicast unsubscribed after subscribing.
This happens because route table subscribe walk is started without initializing
type of walk. In that case disassociate is issued resulting in unsubscription.
This issue will happen if this walk requests are processed after route
notification in controller. Notification would have done sub but walk will
unsub. If walk finishes before route notification then issue is not seen.
Change-Id: I9a3d02d901a1d9 cb4f2755e5c6254 231f35f13f7 9e6c69eafcb1991 d4e5f7d957)
Closes-bug: #1732394
(cherry picked from commit 236dad449e49664