Juniper Openstack

Don't copy import-only RT of VN to route-target-list of default static

Bug #1547930 reported by amit surana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.0
Fix Committed
High
Sachin Bansal
Juniper Openstack r3.0-fcs
Trunk
Fix Committed
High
Sachin Bansal
Juniper Openstack r3.1.0.0-fcs

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 spoke VNs is connected to a LR, the default static route is tagged with RT-2. As such, this route will be imported by all the spoke VNs, even though they aren't connected to a LR.

See original description
Tags: blocker config
amit surana (asurana-t)
summary: - Don't copy import-only RT to import-list of snat RI
+ Don't copy import-only RT of VN to import-list of snat RI
amit surana (asurana-t)
tags: added: blocker
amit surana (asurana-t)
description: updated
summary: - Don't copy import-only RT of VN to import-list of snat RI
+ Don't copy import-only RT of VN to route-target-list of default static
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/17660
Submitter: Sachin Bansal (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.0

Review in progress for https://review.opencontrail.org/17714
Submitter: Sachin Bansal (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/17660
Committed: http://github.org/Juniper/contrail-controller/commit/e4bdb03ef4007e9a8d9546f40cbb138556f97ec1
Submitter: Zuul
Branch: master

commit e4bdb03ef4007e9a8d9546f40cbb138556f97ec1
Author: Sachin Bansal <email address hidden>
Date: Mon Feb 22 14:44:24 2016 -0800

Use import-only/export-only route targets only for primary RI

They are created primarily for hub-spoke topologies. Using them for
service instances/logical routers/transit networks causes unexpected
behavior. Restrict their usage to primary RI only.

Change-Id: I72bd3a78a96c4a3872788fce2c00113ea388e9ec
Closes-Bug: 1547933
Closes-Bug: 1547930

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/17714
Committed: http://github.org/Juniper/contrail-controller/commit/66cba1dbb520fbb8665de96b09a7f639f5d6ed61
Submitter: Zuul
Branch: R3.0

commit 66cba1dbb520fbb8665de96b09a7f639f5d6ed61
Author: Sachin Bansal <email address hidden>
Date: Mon Feb 22 14:44:24 2016 -0800

Use import-only/export-only route targets only for primary RI

They are created primarily for hub-spoke topologies. Using them for
service instances/logical routers/transit networks causes unexpected
behavior. Restrict their usage to primary RI only.

Change-Id: I72bd3a78a96c4a3872788fce2c00113ea388e9ec
Closes-Bug: 1547933
Closes-Bug: 1547930
(cherry picked from commit e4bdb03ef4007e9a8d9546f40cbb138556f97ec1)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.