Route towards SNAT SI continued to be present even after removing the subnet from router
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R1.1 |
Fix Committed
|
High
|
Sachin Bansal | |||
Trunk |
Fix Committed
|
High
|
Sachin Bansal |
Bug Description
R1.10 31
During a tempest run, a VM (in private VN) had both floatingip and router-
We then removed the interface attached to the router.
It was expected that the route for 0.0.0.0/0 from the VRF of the private VN should go away, but it continued to be present.
Ping from the VM to external world failed.
In the control node, the static route object continued to point to the RT of the private VN.
Restarting supervisor-config and control-node didnt help either
Logs will be in http://
root@nodea9:
root@nodea9:
+------
| Field | Value |
+------
| admin_state_up | True |
| contrail:fq_name | default-domain |
| | TestNetworkAdva
| | router-
| external_
| id | 57ca16db-
| name | router-
| status | ACTIVE |
| tenant_id | ada60ec46065433
+------
root@nodea9:
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| e3f74648-
+------
root@nodea9:
In control-node :
<iq>
<service-
<routing-
<prefix>
<service-
<service-
<source-
</service-
<static-
<route>
<prefix>
<next-
<route-
</route>
</static-
</iq>
root@nodea9:
n+-----
| id | name | subnets |
+------
| bbc8b235-
| b760271b-
| 71c058fd-
| f02fd20e-
| 4c2d76de-
+------
root@nodea9:
vrouter-
vrouter-
root@nodea9:
tags: | added: blocker |
The router- gateway- clear is not executed. Right now, routes are withdrawn and SI is deleted as part of router- gateway- clear.
Marking the bug as invalid.
-Divakar