Comment 6 for bug 1495002

Nova-compute does not send delete to agent when add/delete is performed continuously. Script to recreate the issue is attached. The script does add and delete of VMs repeatedly. (net-id has to replaced appropriately when reusing the script)

Some logs associated with instance UUID of interface for which delete is not recevied are pasted below.

15522:2016-03-01 14:37:12.426 22068 AUDIT nova.compute.manager [req-4879a34c-ecc5-4a59-943c-d98d65b25eda None] [instance: 025fab58-a8e2-40a9-978c-bef78d1d1d3c] Terminating instance
15538:2016-03-01 14:37:13.079 22068 INFO nova.virt.libvirt.driver [-] [instance: 025fab58-a8e2-40a9-978c-bef78d1d1d3c] Instance destroyed successfully.
15650:2016-03-01 14:37:14.444 22068 DEBUG nova.compute.manager [-] [instance: 025fab58-a8e2-40a9-978c-bef78d1d1d3c] Synchronizing instance power state after lifecycle event "Started"; current vm_state: active, current task_state: None, current DB power_state: 1, VM power_state: 1 handle_lifecycle_event /usr/lib/python2.7/dist-packages/nova/compute/manager.py:1126
15835:2016-03-01 14:37:16.744 22068 INFO nova.compute.manager [-] [instance: 025fab58-a8e2-40a9-978c-bef78d1d1d3c] VM Stopped (Lifecycle Event)
15862:2016-03-01 14:37:18.640 22068 WARNING nova.compute.manager [-] [instance: 025fab58-a8e2-40a9-978c-bef78d1d1d3c] Instance shutdown by itself. Calling the stop API. Current vm_state: active, current task_state: None, current DB power_state: 4, current VM power_state: 4