Designate and neutron - only creating records for floating ips and not servers or ports
Hi We have a problem where we can create a floating ip and the neutron integration happily creates the dns record. However, if we create a port or a server the record does not get created. This is a charm installation, with designate using designate-bind as the backend. Any suggestions or places to look would be appreciated. I can't see any errors in the designate logs or the neutron logs. Thanks Russell
Hi Russell, This sounds like you are trying to set up "case 3" as described in the neutron documentation[1]. I would start by walking through this document to make sure the right extensions are enabled in neutron. Also note the requirements the extensions have listed in this section: https://docs.openstack.org/neutron/2023.1/admin/config-dns-int-ext-serv.html... I'm pretty sure this is a configuration issue on the neutron extension side, but just to be sure, you can watch the Designate API log when you create a port. If there is no request from neutron, it's getting blocked prior to sending the request to Designate. Michael [1] https://docs.openstack.org/neutron/2023.1/admin/config-dns-int-ext-serv.html... On Tue, May 23, 2023 at 8:29 AM Russell Stather <Russell.Stather@ignitiongroup.co.za> wrote:
Hi
We have a problem where we can create a floating ip and the neutron integration happily creates the dns record.
However, if we create a port or a server the record does not get created.
This is a charm installation, with designate using designate-bind as the backend.
Any suggestions or places to look would be appreciated.
I can't see any errors in the designate logs or the neutron logs.
Thanks
Russell
participants (2)
-
Michael Johnson
-
Russell Stather