Don't copy export-only RT of VN to export-list of SI RI
Bug #1547933 reported by
amit surana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
High
|
Sachin Bansal | |||
Trunk |
Fix Committed
|
High
|
Sachin Bansal |
Bug Description
Consider a hub-and-spoke topology, where spoke VNs are exporting their routes with RT-1 and importing only hub VN routes via RT-2. Now, if one of the spoke VNs is connected via a service-chain to another spoke VN (or some other non-spoke VN), both the SI RIs copy the export-only RT, RT-1, from the VNs to their respective export-list. This will cause the hub VN to see 2 routes to the spoke VNs: one direct route (from importing RT-1 from the spoke VNs) and another via the SC re-originated route which also has RT-1. This is undesirable.
Review in progress for https:/ /review. opencontrail. org/17660
Submitter: Sachin Bansal (<email address hidden>)