I am having some issue with OpenStack Designate that whenever I use the 'designate-manage update pool' command my PTR records are unset but the actual records stay active in the reverse zone. I have tried finding the problem but sadly I cannot pinpoint where and why to problem occurs.
The screenshots below are from our development environment deployed using Kolla-Ansible. But the same happens within a new devstack environment. The problems occurs in the versions "stable/2023.1" and "stable/yoga" I have reproduced this using Devstack and using a Kolla-Ansible deployment in "stable/2023.1".
Screenshots:
(ptr record list) Before designate-manage update pool:
https://jhcsmedia.com/?f=qx2V6EAboABR7tx1Jjm7Dt26bi8hRKEd.png
(ptr record list) After designate-manage update pool:
https://jhcsmedia.com/?f=FL1bn7dAmU0lczsai2p3qS1zLu1ye21R.png
(record list) Records in zone after designate-manage update pool:
https://jhcsmedia.com/?f=hNUSSz1XB92BYixtI9N6KVyy53SjzmqA.png
How to reproduce in DevStack?
1. Install DevStack with OpenStack designate installed the Local.conf I used below:
[[local|localrc]]
ADMIN_PASSWORD=<password>
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD
HOST_IP=<ip-address>
SERVICE_HOST=$HOST_IP
# Enable designate
enable_plugin designate https://opendev.org/openstack/designate
enable_service designate,designate-central,designate-api,designate-worker,designate-producer,designate-mdns,designate-sink
2. After devstack has been installed create a Floating IP:
openstack floating ip create public
3. Now set a PTR record for the Floating IP
openstack ptr record set <Region (RegionOne)>:<Floating IP UUID> devstack.example.com.
4. Wait until the record has been set as "ACTIVE" in the reverse zone (don't know if this is required of not)
openstack record list --all <reverse_zone_id>. (Use --all because the zone is place under the 00000000-0000-0000-0000-000000000000 project)
5. Update the designate pool using the command: designate-manage update pool With or without the pools.yaml file has the same effect.
designate-manage pool update [--file /etc/designate/pools.yaml]
6. Wait for the designate-manage pool update to finish after which the PTR record will be shown as empty (None) using the ptr record list command even tough they are still listed in the zone when u use the record list command again
openstack ptr record list
openstack record list --all <reverse_zone_id>
It almost seems like the records are removed from the database and are then are put back with a new ID and without the ptr:floatingip and managed_resource_id, tenant_id and managed_tenant_id fields filled.
If any more information is required or if I can help in any way please let me know.
Fix proposed to branch: master
Review: https:/