[R2.22.2-12]: deleted VM still present in agent, causing lots of failure in sanity

[alok kumar]

sanity report- http://10.204.216.50/Docs/logs/2.22.2-12_2016_05_11_21_28_24/junit-noframes.html

here lots of tests failed because deleted VMs were present in agent.
I tried running one test case and able to reproduce it each time.

test case: TestDetailedPolicy0.test_repeated_policy_modify

VM created with id: 28a8f289-b4f2-45df-8650-d9439085c1c8

after deletion, this id in not present in API but in agent it's still present.

setup info- same as mentioned in the sanity report.

Config Nodes : [u'nodei13-vm1', u'nodek7-vm1']
Control Nodes : [u'nodei13-vm1', u'nodek7-vm1']
Compute Nodes : [u'nodeg28', u'nodeg29', u'nodeg30']
Openstack Node : nodek7-vm1
WebUI Node : nodei14-vm1
Analytics Nodes : [u'nodei13-vm1', u'nodek7-vm1']
Physical Devices : [u"'hooper'"]

[alok kumar (kalok)]

this is docker setup.

VM 28a8f289-b4f2-45df-8650-d9439085c1c8 info can be found at node http://nodeg28:8085/Snh_VmListReq?uuid=

[Ashok Singh (ashoksr)]

Agent has not received delete for interfaces from docker plugin.

In nodeg28, interfaces 870fb0ef-8ef0-4872-bfa7-b976ac21928e and a20c93f0-abc3-46ba-96c0-909861fa4622 are in error state (http://nodeg28:8085/Snh_ItfReq?name=&type=&uuid=&vn=&mac=&ipv4_address=&ipv6_address=&parent_uuid=&ip_active=&ip6_active=&l2_active=)

For both these interfaces, agent has not received delete (http://nodeg28:8085/Snh_SandeshTraceRequest?x=Config)