When more than one subnet of a VN is added to a router, snat fails when one of the subnets are deleted from it
Bug #1381019 reported by
Vedamurthy Joshi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.0 |
New
|
Medium
|
Rudra Rugge | |||
| Trunk |
Invalid
|
Medium
|
Unassigned | |||
Bug Description
R1.10 Build 52 Ubuntu multi-node on Icehouse
On VN1, have subnets S1 and S2.
Add S1 and S2 to router rtr1 with gateway vn G1
snat works for both S1 and S2
Remove S1 from rtr1
snat from S2 starts to fail
The VRF of VN1 lost the 0.0.0.0/0 route to veth
| summary: |
- When more than one subnet is added to a router, snat fails when one of - the subnets are deleted from it + When more than one subnet of a VN is added to a router, snat fails when + one of the subnets are deleted from it |
Revision history for this message
| Nischal Sheth (nsheth) wrote | #2 |
To post a comment you must log in.
I checked the code. svc-monitor is removing link from vn to route table when a port is removed from router even though there is another port from the same VN connected to the router. In 3.1, this will be fixed by our changes to link router directly to route table, but for older releases, svc-monitor needs to fix.