With the introduction of same RD for Tor agent for vrf, change of vnid was not
handled. In cases where a vn was added with vnid as not set or 0 and then
updated later with non zero value, vrf was not notified.
This used to result in skipping of notify registeration for the problematic vrf.
In turn subscriptions were missed.
Solution:
Handle vnid change.
Change-Id: I7ea7332eb1e64cb0e534f992ef5c8680a54b0313
Closes-bug: #1692795
(cherry picked from commit 8a922e38bfd1e6b2a720d4293fcdf87002cb5a26)
Reviewed: https:/ /review. opencontrail. org/32700 github. com/Juniper/ contrail- controller/ commit/ bb5a441987b02c1 356a7f5b9c0a944 df73fcd2e3
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.2
commit bb5a441987b02c1 356a7f5b9c0a944 df73fcd2e3
Author: Manish <email address hidden>
Date: Thu Jun 8 01:17:30 2017 +0530
BUM tree subscription skipped.
With the introduction of same RD for Tor agent for vrf, change of vnid was not
handled. In cases where a vn was added with vnid as not set or 0 and then
updated later with non zero value, vrf was not notified.
This used to result in skipping of notify registeration for the problematic vrf.
In turn subscriptions were missed.
Solution:
Handle vnid change.
Change-Id: I7ea7332eb1e64c b0e534f992ef5c8 680a54b0313 2a720d4293fcdf8 7002cb5a26)
Closes-bug: #1692795
(cherry picked from commit 8a922e38bfd1e6b