Designate charm does not work with multiple interfaces/network space bindings

[David Coronel]

In a HA-Setup, Designate charm deployed under mitaka and xenial using cs:~openstack-charmers-next/designate-55

Initial deployment works, but after deployment unable to create a domain or do any CLI-Calls:

designate domain-create --name test.url. --email <email address hidden>
ERROR: Unable to establish connection to http://<ip redacted>:9001/domains

It looks like this charm does not support multiple interfaces. It's possible to configure charm to use multiple spaces but the application itself gets bound to the first IP and causes API-Calls on the external address to be blocked.

The same thing happens with the murano charm: https://bugs.launchpad.net/charm-murano/+bug/1733880

One workaround is to download the charm and edit
~/charms/xenial/murano/templates/mitaka/designate.conf:

# Address to bind the API server
api_host = 0.0.0.0

Maybe the fix should be for the charm to detect all available spaces and add those IP addresses to bind to all necessary interfaces?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/523853

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/523853
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=ad6f784696d58a028821c52a017058193998d826
Submitter: Zuul
Branch: master

commit ad6f784696d58a028821c52a017058193998d826
Author: Alex Kavanagh <email address hidden>
Date: Wed Nov 29 11:58:36 2017 +0000

    Enable designate to list on all interfaces

    This is a fix to enable designate to listen on all interfaces when the
    charm designate is installed on a unit with multiple interfaces.

    Change-Id: I96f23532d18550d0e27153d60f1003016958985b
    Closes-Bug: #1734156