Route towards SNAT SI continued to be present even after removing the subnet from router

Bug #1365322 reported by Vedamurthy Joshi
6
This bug affects 1 person
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-with-external-gateway configured.

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://10.204.216.50/Docs/bugs/#

root@nodea9:/var/log/contrail# neutron router-port-list router-smoke--1358609393

root@nodea9:/var/log/contrail# neutron router-show router-smoke--1358609393
+-----------------------+--------------------------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------------------------+
| admin_state_up | True |
| contrail:fq_name | default-domain |
| | TestNetworkAdvancedServerOps-449800564 |
| | router-smoke--1358609393 |
| external_gateway_info | {"network_id": "71c058fd-a72a-4649-98e1-f3235c35acd9"} |
| id | 57ca16db-e1e7-4a26-8809-2169f473ef74 |
| name | router-smoke--1358609393 |
| status | ACTIVE |
| tenant_id | ada60ec460654337844b193e853c8ab2 |
+-----------------------+--------------------------------------------------------+
root@nodea9:/var/log/contrail# nova list
+--------------------------------------+-----------------------------+--------+------------+-------------+-----------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-----------------------------+--------+------------+-------------+-----------------------------------------------------+
| e3f74648-9ee0-4995-8ab6-25281b67cc2e | server-smoke-%d--1356115080 | ACTIVE | None | Running | network-smoke--200760371=10.100.0.2, 10.204.219.204 |
+--------------------------------------+-----------------------------+--------+------------+-------------+-----------------------------------------------------+
root@nodea9:/var/log/contrail#

In control-node :
<iq>
 <service-chain-information>
  <routing-instance>default-domain:admin:public_net:public_net</routing-instance>
  <prefix>10.204.219.200/29</prefix>
  <service-chain-address>100.64.0.5</service-chain-address>
  <service-instance>default-domain:TestNetworkAdvancedServerOps-449800564:si_57ca16db-e1e7-4a26-8809-2169f473ef74</service-instance>
  <source-routing-instance>default-domain:TestNetworkAdvancedServerOps-449800564:svc-snat-si_57ca16db-e1e7-4a26-8809-2169f473ef74:svc-snat-si_57ca16db-e1e7-4a26-8809-2169f473ef74</source-routing-instance>
 </service-chain-information>
 <static-route-entries>
  <route>
   <prefix>0.0.0.0/0</prefix>
   <next-hop>100.64.0.5</next-hop>
   <route-target>target:64510:8000021</route-target>
  </route>
 </static-route-entries>
</iq>

root@nodea9:/var/log/contrail# neutron net-list
n+--------------------------------------+--------------------------------------------------+----------------------------------------------------+
| id | name | subnets |
+--------------------------------------+--------------------------------------------------+----------------------------------------------------+
| bbc8b235-86b2-46fd-8c8f-6b2e92b3d99d | TestNetworkAdvancedServerOps-1623152575-network | 4b72ee13-6ddd-4579-9410-f9d50900ec08 10.100.0.0/28 |
| b760271b-1cc8-46bf-a4ef-b5f986035fdf | network-smoke--200760371 | e7259396-7962-4f27-b974-5cd4b9731556 10.100.0.0/28 |
| 71c058fd-a72a-4649-98e1-f3235c35acd9 | public_net | 36dfe01d-9c31-46c1-8646-dfe1558ddb3e |
| f02fd20e-ef73-4505-94f6-6a5d79e6b3dd | svc-snat-si_f5c5cec0-0fc9-4543-9f8d-c998f7bd7200 | b21f7449-a2d0-41c5-ac03-5d6c3caa1127 100.64.0.0/29 |
| 4c2d76de-042f-4bf0-a4db-59fbe75fb9cd | svc-snat-si_57ca16db-e1e7-4a26-8809-2169f473ef74 | e5558bfa-0e19-4791-985b-3a25e48050f0 100.64.0.0/29 |
+--------------------------------------+--------------------------------------------------+----------------------------------------------------+
root@nodea9:/var/log/contrail# ip netns list
vrouter-9bdfac4e-60ec-4df3-ba9f-6af54be329ee
vrouter-fc64eab5-38ae-4fe0-800d-d3c1fecd53ad
root@nodea9:/var/log/contrail#

tags: added: blocker
Revision history for this message
Divakar Dharanalakota (ddivakar) wrote :

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

Revision history for this message
Vedamurthy Joshi (vedujoshi) wrote :

Talked to Divakar . He incorrectly moved the bug to invalid. The route for 0.0.0.0 should be withdrawn on router-interface-delete

Revision history for this message
Sachin Bansal (sbansal) wrote :

Already fixed in mainline with commit 4196290833e41fc9488d2ec119ddb77597cb5a94

Revision history for this message
Rudra Rugge (rrugge) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.