I was able to reproduce this. It's specific to coordination backend code that is used for HA. For charms, the following bundle config was used (snipped for brevity to just show designate bits):
hacluster-designate: charm: cs:hacluster options: cluster_count: 2 designate: charm: cs:~openstack-charmers-next/designate constraints: mem=1G num_units: 2 options: action-managed-upgrade: true debug: true nameservers: 'ns1.ubuntu.com' nova-domain: 'serverstack.ubuntu.com.' neutron-domain: 'serverstack.ubuntu.com.' nova-domain-email: '<email address hidden>' neutron-domain-email: '<email address hidden>' vip: 10.5.20.1 designate-bind: charm: cs:~openstack-charmers-next/designate-bind relations: - [ designate, keystone ] - [ designate, mysql ] - [ designate, rabbitmq-server ] - [ designate, designate-bind ] - [ designate, memcached ] - [ designate, hacluster-designate ] - - designate:dnsaas - neutron-api:external-dns
I was able to reproduce this. It's specific to coordination backend code that is used for HA. For charms, the following bundle config was used (snipped for brevity to just show designate bits):
hacluster- designate:
cluster_ count: 2 charmers- next/designate
action- managed- upgrade: true
nameservers: 'ns1.ubuntu.com'
nova-domain: 'serverstack. ubuntu. com.'
neutron- domain: 'serverstack. ubuntu. com.'
nova-domain- email: '<email address hidden>'
neutron- domain- email: '<email address hidden>' charmers- next/designate- bind api:external- dns
charm: cs:hacluster
options:
designate:
charm: cs:~openstack-
constraints: mem=1G
num_units: 2
options:
debug: true
vip: 10.5.20.1
designate-bind:
charm: cs:~openstack-
relations:
- [ designate, keystone ]
- [ designate, mysql ]
- [ designate, rabbitmq-server ]
- [ designate, designate-bind ]
- [ designate, memcached ]
- [ designate, hacluster-designate ]
- - designate:dnsaas
- neutron-