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.
Reviewed: https:/ /review. opencontrail. org/21794 github. org/Juniper/ contrail- controller/ commit/ f9eca51ca02ac7b bea1e592aa195f2 65e8fe7937
Committed: http://
Submitter: Zuul
Branch: R2.22.x
commit f9eca51ca02ac7b bea1e592aa195f2 65e8fe7937
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.
Change-Id: Ia3c11ad71558a6 e9e215bbb6817cc d9f65253a5d
Closes-Bug: #1596792