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.
Reviewed: https:/ /review. opencontrail. org/33685 github. com/Juniper/ contrail- controller/ commit/ 72efe8e70cc65b6 029d3e7f322003d aadd36ec64
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R4.0
commit 72efe8e70cc65b6 029d3e7f322003d aadd36ec64
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.
Closes-bug: #1692795
Conflicts: agent/controlle r/controller_ vrf_export. cc agent/oper/ agent_route_ walker. cc agent/oper/ vrf.cc agent/oper/ vrf.h
src/vnsw/
src/vnsw/
src/vnsw/
src/vnsw/
Conflicts: agent/oper/ vrf.h b0e534f992ef5c8 680a54b0313
src/vnsw/
Change-Id: I7ea7332eb1e64c