I find out this is exactly a bug in designate. not related to kolla-ansible.
the default_pool_id config under section [service:central] does not work properly when running command "designate-manage database xxx" or "designate-manage pool xxxx".
the code in manage.py says, even if we execute "designate-manage database", we also load the default cli params for command "designate-manage pool"
then the code in pool.py, it is recursively defined default_pool_id from cli by the default opts values in conf. that means "register_default_opts" <-- overwrite by real conffile <-- overwrite again by cli default opts.
I think we need someone help from designate project to suggest how to fix it in designate.
duplicate: https:/ /bugs.launchpad .net/designate/ +bug/1881277
I find out this is exactly a bug in designate. not related to kolla-ansible.
the default_pool_id config under section [service:central] does not work properly when running command "designate-manage database xxx" or "designate-manage pool xxxx".
This is because the code below: /opendev. org/openstack/ designate/ src/branch/ master/ designate/ cmd/manage. py#L59 /opendev. org/openstack/ designate/ src/branch/ master/ designate/ manage/ pool.py# L65
https:/
https:/
the code in manage.py says, even if we execute "designate-manage database", we also load the default cli params for command "designate-manage pool"
then the code in pool.py, it is recursively defined default_pool_id from cli by the default opts values in conf. that means "register_ default_ opts" <-- overwrite by real conffile <-- overwrite again by cli default opts.
I think we need someone help from designate project to suggest how to fix it in designate.