FloatingIP entry is not removed after VM delete

[Alex Stafeyev]

AIO setup.
Backend BIND
SINK for nova and neutron enabled.

When we create a vm a record created
When we assign FIP to VM a record created.
When we delete the VM only the nova record deleted. FIP record remains.

[root@controller ~(keystone_admin)]# designate record-list $DOMAINID
+--------------------------------------+------+--------------------------+-------------------------------------------------------------------------+
| id | type | name | data |
+--------------------------------------+------+--------------------------+-------------------------------------------------------------------------+
| 3d28786b-b0d8-434c-8b20-0e34363a9b17 | SOA | example.com. | controller.novalocal2. root.example.com. 1441627367 3600 600 86400 3600 |
| 912818ef-a043-48bc-9c73-a621d930c40d | NS | example.com. | controller.novalocal2. |
| e55985e6-79d1-4fb1-8671-8fe895def7a5 | A | server1.example.com. | 1.2.3.4 |
| 97c8270f-845b-41df-9537-1d135e3a0a50 | A | vm10.example.com. | 192.168.1.19 |
| 21bc94da-73bf-4f20-b61a-1cd6d90dac70 | A | 10-35-187-4.example.com. | 10.35.187.4 |
+--------------------------------------+------+--------------------------+-------------------------------------------------------------------------+
[root@controller ~(keystone_admin)]# nova delete vm10
Request to delete server vm10 has been accepted.
[root@controller ~(keystone_admin)]# designate record-list $DOMAINID
+--------------------------------------+------+--------------------------+-------------------------------------------------------------------------+
| id | type | name | data |
+--------------------------------------+------+--------------------------+-------------------------------------------------------------------------+
| 3d28786b-b0d8-434c-8b20-0e34363a9b17 | SOA | example.com. | controller.novalocal2. root.example.com. 1441628460 3600 600 86400 3600 |
| 912818ef-a043-48bc-9c73-a621d930c40d | NS | example.com. | controller.novalocal2. |
| e55985e6-79d1-4fb1-8671-8fe895def7a5 | A | server1.example.com. | 1.2.3.4 |
| 21bc94da-73bf-4f20-b61a-1cd6d90dac70 | A | 10-35-187-4.example.com. | 10.35.187.4 |
+--------------------------------------+------+--------------------------+-------------------------------------------------------------------------+
[root@controller ~(keystone_admin)]#

LOGS-
http://pastebin.com/ZUi5vmmb

openstack-designate-api-2015.1.0-1.el7ost.noarch
openstack-designate-agent-2015.1.0-1.el7ost.noarch
openstack-designate-sink-2015.1.0-1.el7ost.noarch
python-designate-2015.1.0-1.el7ost.noarch
openstack-designate-mdns-2015.1.0-1.el7ost.noarch
python-designateclient-1.2.0-1.el7ost.noarch
openstack-designate-common-2015.1.0-1.el7ost.noarch
openstack-designate-central-2015.1.0-1.el7ost.noarch
openstack-designate-pool-manager-2015.1.0-1.el7ost.noarch

[Graham Hayes (grahamhayes)]

The neutron listener does not listen for the "detach" event, just the delete.

[naggappan (naggappan)]

Hi Team if this is not much critical bug, Please assign to me, I will try to fix it. Already i am working on to recreate this issue