[Mainline-3029]: Routes are not leaked when policy is attached to VNs
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.2 |
Fix Committed
|
Critical
|
Sahil Sabharwal | |||
| Trunk |
Fix Committed
|
Critical
|
Sahil Sabharwal | |||
Bug Description
This is basic policy test where the policy is attached to 2 VNs and then ping to from 1 VN to other one.
This is failing and after debugging it's found that routes are not leaked into vrfs where policy is attached(verified it in control node too).
test steps:
1. Create 2 VNs, say 1.1.1.0/24 and 2.2.2.0/24
2. launch 1 VM in each.
3. create the policy to allow all traffic between these VNs and attach it to both VNs.
4. now ping from VN1 to VN2.
config details:
Display Name
pol1
UUID
552bf96f-
Connected networks
vn1
vn2
Rules
pass protocol any network vn1 ports any <> network vn2 ports any
VNs:
https:/
control node routes for vn1:
http://
setup details:
please use nodeg24 to debug, it's a single node setup.
| OpenContrail Admin (ci-admin-f) wrote [Review update] master | #1 |
| tags: | added: blocker |
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #3 |
| OpenContrail Admin (ci-admin-f) wrote [Review update] R3.2 | #4 |
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #6 |
| information type: | Proprietary → Public |
Review in progress for https:/
Submitter: <email address hidden> (<email address hidden>)