Designate (zed/stable) not TLS aware

[Courtney Oakley]

OVERVIEW OF ENVIRONMENT
Charmed Openstack Zed/Stable-Jammy across 13 R-Series servers - 1/2 TB RAM and 90 vCPUs
Vault HA
Nova-Cloud-Controller HA
Keystone HA
Mysql-Innodb_cluster HA (X3)
Rabbitmq-Server HA (X3)
Octavia
Aodh
Barbican
Barbican-Vault
Ceilometer
Gnocchi
Heat

PROBLEM DESCRIPTION
Designate does not detect that an installation is TLS and change the Endpoints to https:// accordingly.

It also fails to call Keystone with the https:// keystone endpoint resulting in a 503 error.

Adding a Vault relation does not impact the issue - it has no effect.

EXPECTED RESULT
Designate changes endpoints to https://. Designate calls Keystone correctly using https:// endpoint for Keystone.

STEPS TO REPRODUCE
juju deploy designate
juju deploy designate-bind
........
juju add-relation designate designate-bind

[Alex Kavanagh (ajkavanagh)]

Thanks for the bug report. We need a little more information, please, to work out what's going on. Please could you read of

https://docs.openstack.org/charm-guide/yoga/community/software-bug.html

It's just that these are very complicated systems and we need as much information as possible to understand what might be going on so we can help sort it out.

Many thanks!

[Launchpad Janitor (janitor)]

[Expired for OpenStack Designate Charm because there has been no activity for 60 days.]