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/3824 github. org/Juniper/ contrail- controller/ commit/ 6119e734257f355 95c3571b033bd0d 7788494a90
Committed: http://
Submitter: Zuul
Branch: master
commit 6119e734257f355 95c3571b033bd0d 7788494a90
Author: Nischal Sheth <email address hidden>
Date: Wed Oct 15 13:52:21 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: Ifdff8e828f0d4a 9bc20ab055e0e92 06d2cfd347a
Partial-Bug: 1365277