Fix circular route re-origination bug with transit VN
Problem:
When a service is applied between a VN and a transit VN, routes from the
VN that are re-originated into the transit VN as ServiceChain routes get
re-originated again as ServiceChain routes into the regular VN.
Cause:
Implementation prior to transit VN used to ignore routes that did belong
to the destination VN of the service chain. Code changes for transit VN
functionality relaxed this check, but did not cover the case where route
belongs to the source VN.
Reviewed: https:/ /review. opencontrail. org/3826 github. org/Juniper/ contrail- controller/ commit/ 7b102a5cf7bd0f9 43f71d2e03f1adf af2828c9cc
Committed: http://
Submitter: Zuul
Branch: R1.10
commit 7b102a5cf7bd0f9 43f71d2e03f1adf af2828c9cc
Author: Nischal Sheth <email address hidden>
Date: Thu Oct 16 11:44:26 2014 -0700
Fix circular route re-origination bug with transit VN
Problem:
When a service is applied between a VN and a transit VN, routes from the
VN that are re-originated into the transit VN as ServiceChain routes get
re-originated again as ServiceChain routes into the regular VN.
Cause:
Implementation prior to transit VN used to ignore routes that did belong
to the destination VN of the service chain. Code changes for transit VN
functionality relaxed this check, but did not cover the case where route
belongs to the source VN.
Fix:
Add check to ignore routes from source VN.
Change-Id: Ic6f5520217eca6 4b79f5144d71f80 aa6d661e48a
Partial-Bug: 1365277