Interesting, I deleted every mention of designate from your local.conf and it deployed successfully.
At some point I got the following error from designate:
/opt/stack/designate/devstack/designate_plugins/backend-bind9: line 40: is_suse: command not found
That made me think that designate uses/depends on old code (is_suse doesn't exist in devstack anymore), therefore I tried to run it without designate service which surprisingly worked.
I think that the root cause will be somewhere in 'old code' which might be included accidentally. The local.conf you shared may contain old extensions that include the 'old code'. That's something frickler raised as well during our last office hour: https://meetings.opendev.org/meetings/qa/2023/qa.2023-09-19-15.00.log.html#l-116
Interesting, I deleted every mention of designate from your local.conf and it deployed successfully.
At some point I got the following error from designate: designate/ devstack/ designate_ plugins/ backend- bind9: line 40: is_suse: command not found
/opt/stack/
That made me think that designate uses/depends on old code (is_suse doesn't exist in devstack anymore), therefore I tried to run it without designate service which surprisingly worked.
I think that the root cause will be somewhere in 'old code' which might be included accidentally. The local.conf you shared may contain old extensions that include the 'old code'. That's something frickler raised as well during our last office hour: /meetings. opendev. org/meetings/ qa/2023/ qa.2023- 09-19-15. 00.log. html#l- 116
https:/