Remove the assumption that VN of an interface cannot change without first getting a
notification for NULL VN.
Also fix the following issue.
Also when VN changes for a VMI (clubbing of VMI getting NULL VRF and later new VRF
events into a single event) we were not removing EVPN and Bridge routes for old VRF.
Also added UT to verify this scenario.
Closes-Bug: #1596792
(cherry picked from commit 64ef02488ed11d637a46f5b8c51664838cf2b95c)
Reviewed: https:/ /review. opencontrail. org/21796 github. org/Juniper/ contrail- controller/ commit/ 2656b8ca109dc46 8545a5a74300714 affaaed435
Committed: http://
Submitter: Zuul
Branch: R2.20
commit 2656b8ca109dc46 8545a5a74300714 affaaed435
Author: ashoksingh <email address hidden>
Date: Mon Jul 11 10:54:12 2016 +0530
Handle VN change in interface Notification
Remove the assumption that VN of an interface cannot change without first getting a
notification for NULL VN.
Also fix the following issue.
Also when VN changes for a VMI (clubbing of VMI getting NULL VRF and later new VRF
events into a single event) we were not removing EVPN and Bridge routes for old VRF.
Also added UT to verify this scenario.
Closes-Bug: #1596792 37a46f5b8c51664 838cf2b95c)
(cherry picked from commit 64ef02488ed11d6
Change-Id: I037631d09af36e 7d191cc0f45a129 a99d3c800ea