control-node ifmap continued to have snat si even after router is deleted

R1.10 44 (Ubuntu icehouse multinode setup)

In the test test_basic_snat_behavior_with_subnet_attach_detach in contrail-test, it creates snat setup, removes the VN interface from the router, adds the VN back again and finally cleans up everything.

At the end of it, the script failed because the VN object in control-node config db continued to exist even after the VN and router was deleted.
It was seen that the snat VM's instance IP continued to refer to the VN in control-node config.

The VN is virtual-network:default-domain:TestRouters-82931130:ext_vn-51078609

In control-node introspect : ifmap table entry :
virtual-network:default-domain:TestRouters-82931130:ext_vn-51078609
- - -
obj_info
neighbors
instance-ip:si_808bbb6b-dc7b-4020-8cce-4816611b85ce-right
00:38:46.051751

Logs will be in http://10.204.216.50/Docs/bugs/#

root@nodec22:/var/log/contrail# neutron net-list
+--------------------------------------+-------------------------+---------------------------------------------------+
| id | name | subnets |
+--------------------------------------+-------------------------+---------------------------------------------------+
| dd32ac7e-527c-486f-addb-4118a65ed43a | default-virtual-network | |
| d9efaf6b-d60c-4b48-b5e7-89ce4b29647c | ip-fabric | |
| eae8c123-451b-43cb-948d-d37ec2c827d5 | vn1-31619381 | 0bc7104c-1a59-47ec-ad19-6fbc6dbab0b5 51.6.68.0/24 |
| 2993df96-842a-4f5f-b7f8-93fa36e37a04 | __link_local__ | |
+--------------------------------------+-------------------------+---------------------------------------------------+
root@nodec22:/var/log/contrail#

test logs :
=========
2014-10-04 05:42:38,453 - INFO - Deleting interface with subnet_id aca8ed2d-e966-4304-a6a3-c66d7aaf410f, port_id None from router 808bb
b6b-dc7b-4020-8cce-4816611b85ce
2014-10-04 05:42:39,062 - INFO - Deleting the VM vm_public-53323424
2014-10-04 05:42:44,221 - INFO - Deleting the VM vm_private-26268979
2014-10-04 05:42:49,326 - INFO - Deleting the VN vn_private-41715389
2014-10-04 05:42:49,488 - INFO - VN vn_private-41715389 is not found in API Server
None
2014-10-04 05:42:49,494 - INFO - VN vn_private-41715389 is not present in Agent 10.204.217.69
None
2014-10-04 05:42:49,501 - INFO - VN vn_private-41715389 is not present in Agent 10.204.217.108
None
2014-10-04 05:42:49,507 - INFO - VN vn_private-41715389 is not present in Agent 10.204.217.109
2014-10-04 05:42:49,510 - WARNING - Routing instance for VN vn_private-41715389 is still found in Control-node 10.204.217.7
2014-10-04 05:42:49,513 - WARNING - Routing instance for VN vn_private-41715389 is still found in Control-node 10.204.217.108
2014-10-04 05:42:49,550 - WARNING - Control-node config DB still has VN vn_private-41715389
2014-10-04 05:42:54,601 - INFO - Routing instances and Config db in Control-nodes does not have VN vn_private-41715389 info
2014-10-04 05:42:54,601 - INFO - Deleting RT for VN ext_vn-51078609
2014-10-04 05:42:54,624 - INFO - Deleting the VN ext_vn-51078609
2014-10-04 05:42:55,016 - INFO - VN ext_vn-51078609 is not found in API Server
None
2014-10-04 05:42:55,022 - INFO - VN ext_vn-51078609 is not present in Agent 10.204.217.69
None
2014-10-04 05:42:55,030 - INFO - VN ext_vn-51078609 is not present in Agent 10.204.217.109
2014-10-04 05:42:55,032 - WARNING - Routing instance for VN ext_vn-51078609 is still found in Control-node 10.204.217.7
2014-10-04 05:42:55,036 - WARNING - Routing instance for VN ext_vn-51078609 is still found in Control-node 10.204.217.108
2014-10-04 05:42:55,066 - WARNING - Control-node config DB still has VN ext_vn-51078609
2014-10-04 05:43:00,110 - WARNING - Control-node config DB still has VN ext_vn-51078609
2014-10-04 05:43:05,159 - WARNING - Control-node config DB still has VN ext_vn-51078609
2014-10-04 05:43:10,197 - WARNING - Control-node config DB still has VN ext_vn-51078609