Comment 15 for bug 1696853
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #15 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Reviewed: https:/
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.1.1.x
commit f17813be5dd9d2b
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700
Do not store OriginVn attribute in Locally originated multicast route
Currently, OriginVn value is determined by looking at the virtual_
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.
Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.
Change-Id: I55c894f044b0b3
Closes-Bug: #1696853
(cherry picked from commit 50361eafda88038