Addition and deletion of Connected VNs for SNAT is broken
Bug #1445692 reported by
Sreelakshmi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
Fix Committed
|
High
|
Balamurugan Gopal | |||
R2.1 |
Fix Committed
|
High
|
Balamurugan Gopal | |||
R2.20 |
Fix Committed
|
High
|
Balamurugan Gopal | |||
Trunk |
Fix Committed
|
High
|
Balamurugan Gopal |
Bug Description
Multiple issues noticed when you add/delete VNs to Connected Virtual networks in our SNAT feature.
1. 0/0 route is not withdrawn when we delete a VN from the connected network.
2. addition of new VN to the connected list is not reflected when you incrementally add one VN after another to an existing Router/SNAT GW.
Changed in juniperopenstack: | |
assignee: | nobody → Suresh Balineni (sbalineni) |
importance: | Undecided → High |
information type: | Proprietary → Public |
tags: | added: blocker config |
tags: | added: ui |
To post a comment you must log in.
Issue 1 happens only when router- configuration via Contrail UI. When done using neutron api/cli, things are fine