OpenStack Designate failed to create zones when configuring multiple pools

[Đỗ Hoàng Sơn]

I'm having a problem with OpenStack Designate. When I configure multiple pools and create zone with default pool, zone creation and record creation is successful. But when I go to the zone and record to the other pool, I get an error. Currently, I'm deploying OpenStack using kolla-ansible and two DNS Servers in two pools, BIND9. Looking forward to hearing from everyone. Thank you very much.

I want to be able to successfully create zones and records via OpenStack Designate to two BIND9 DNS Servers.

[Gaël THEROND (gtherond)]

I'll have a look at it.

[Sven Kieske (s-kieske)]

what exactly is the error here? can someone please submit the actual error being fixed here?

[Gaël THEROND (gtherond)]

Here is the error:

TASK [designate : Non-destructive DNS pools update] ****************************
fatal: [nc-controller01 -> nc-controller01]: FAILED! => {"changed": true, "cmd": ["docker", "exec", "-t", "designate_worker", "designate-manage", "pool", "update", "--delete"], "delta": "0:00:01.219159", "end": "2023-03-23 15:05:44.769693", "msg": "non-zero return code", "rc": 1, "start": "2023-03-23 15:05:43.550534", "stderr": "", "stderr_lines": [], "stdout": "Updating Pools Configuration\r\n****************************", "stdout_lines": ["Updating Pools Configuration", "****************************"]}

I've another bug that is related to this:
https://bugs.launchpad.net/kolla-ansible/+bug/1773972
&
https://bugs.launchpad.net/kolla-ansible/+bug/2012292

[Dr. Jens Harbott (j-harbott)]

You can write your own pools.yaml and place it into "{{ node_custom_config }}/designate/pools.yaml". The error message above is incomplete, you need to show the full output from designate-manage.log.

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Gaël THEROND <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/878270
Reason: I'm fed up with those back and forth nonsense.