Record is not deleted after terminating a VM+duplicate records

Bug #1491248 reported by Alex Stafeyev
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Designate
Invalid
Undecided
Graham Hayes

Bug Description

We configured designate to create record when VM goes up.
It works .
When we terminate the VM the record is not deleted.
We created another VM- same name different IP.
record list shows the following :

[root@controller system(keystone_admin)]# designate record-list 50ccd868-f252-460e-813c-b6cae05c1da9
+--------------------------------------+------+----------------------+------------------------------------------------------------------------+
| id | type | name | data |
+--------------------------------------+------+----------------------+------------------------------------------------------------------------+
| 482e441d-5664-43a0-b01c-351bd4b7dc1f | SOA | example.com. | controller.novalocal. root.example.com. 1441199330 3600 600 86400 3600 |
| 640c1fab-d286-4ce7-9f2f-f31e823c1466 | NS | example.com. | controller.novalocal. |
| 6bd3ea54-9251-4b98-97b4-fd2d179f3f4a | A | server1.example.com. | 1.2.3.4 |
| 96684144-d5e0-4a10-90b7-ce1a7371bb7d | A | 1.example.com. | 192.168.1.4 |
| 742c5102-a527-4e6d-aec0-7fc02a085d51 | A | 1.example.com. | 192.168.1.5 |
+--------------------------------------+------+----------------------+------------------------------------------------------------------------+
[root@controller system(keystone_admin)]#

We can see same name for 2 different IPs. --------- 1.example.com

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

Logs

http://pastebin.com/9SvuHphK

Additionally- DB is not updated when VM terminated

Alex Stafeyev (astafeye)
description: updated
Kiall Mac Innes (kiall)
Changed in designate:
assignee: nobody → Graham Hayes (grahamhayes)
Revision history for this message
Graham Hayes (grahamhayes) wrote :

Could not reproduce

Changed in designate:
status: New → Invalid
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.