Designate integration not fully multi region safe

[Erik Olof Gunnar Andersson]

The admin portion of the external dns integration for designate never passes the url or region to the client. This means that the implementation isn't region aware at all.

[Erik Olof Gunnar Andersson (eandersson)]

Confirmed this locally by creating many regions and enabling the external dns integration with designate and enabling allow_reverse_dns_lookup. While the first portion of the code would pick the correct designate region, the admin portion would fail.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/684854
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=654c1f06d583965c4b5a2ae721a7b1f3786dc76a
Submitter: Zuul
Branch: master

commit 654c1f06d583965c4b5a2ae721a7b1f3786dc76a
Author: Erik Olof Gunnar Andersson <email address hidden>
Date: Wed Sep 25 16:34:03 2019 -0700

    Fix designate driver not being fully region aware

    The admin part of the designate implementation, never
    passes the region or url to client. This means that it
    may fail in multi-region situations.

    We fix this by always passing the endpoint
    override to the client every-time it's instantiated.

    We also add an alternative uri for devstack
    when a designate-api port isn't set.

    Closes-Bug: #1845891
    Change-Id: Ia86c3177f1c0a1909a35e55e63b60aec5167124d

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.