[R2.0-Build 12]: route target import issue
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
Fix Released
|
Critical
|
Sachin Bansal | |||
R2.1 |
Fix Committed
|
Critical
|
Sachin Bansal | |||
Trunk |
Fix Committed
|
Critical
|
Sachin Bansal |
Bug Description
topology:
- VN 'public' (10.204.220.192/29) and VN 'vnet1' (9.9.9.0/24) connected with policy(via transparent firewall)
- policy allows all traffic between these VNs
- route target(64512:20001) is added in vnet1. so default route(0.0.0.0/0) leaked in vnet1 and public, as expected
vnet1 connects to MX.
in VN public we see route target 64512:20001 in import list, which seems to be unexpected.
setup is available if anybody wants to take a look.
setup info:
env.roledefs = {
'all': [host1,
'cfgm': [host1,
'openstack'
'control': [host2,host1],
'compute': [host3,host4],
'collector': [host2,host1],
'webui': [host1],
'database': [host1,
'build': [host_build],
}
env.hostnames = {
'all': ['nodec64', 'nodeg18', 'nodeh8', 'nodec11', 'nodec12']
}
information type: | Proprietary → Public |
tags: | removed: contrail-control |
Reviewed: https:/ /review. opencontrail. org/5778 github. org/Juniper/ contrail- controller/ commit/ ccbc8966fc4855a 1aaf68113f96293 7fb962bf95
Committed: http://
Submitter: Zuul
Branch: R2.0
commit ccbc8966fc4855a 1aaf68113f96293 7fb962bf95
Author: Ashish Ranjan <email address hidden>
Date: Thu Dec 18 10:54:40 2014 -0800
Reverting b6ef3fe9. We will take this change later after more discussion in mainline
This will break the support of multiple policy for a service chain.
https:/ /github. com/Juniper/ contrail- controller/ commit/ d3c9608c64d5fd4 2d201099ad2e81b cd2ee45ca1
Closes-Bug: 1403346, 1403590
Change-Id: I857d678ea5ae2e 3cc73dad51dd2e1 b1908e307e8