This bug is still actual, can someone take a look please?
+ field-high as the expected functionality doesn't work (TLS endpoint isn't updated in Keystone database).
Just have checked on freshly Masakari deployment: the endpoint in Keystone is http:// indeed, and:
# the certs are present: root@juju-2d3b82-0-lxd-10:~# ls /etc/apache2/ssl/masakari/ cert_10.35.174.113 cert_10.35.84.244
# but https-related apache conf is empty ~# cat /etc/apache2/sites-enabled/openstack_https_frontend.conf root@juju-2d3b82-0-lxd-10:~#
This bug is still actual, can someone take a look please?
+ field-high as the expected functionality doesn't work (TLS endpoint isn't updated in Keystone database).
Just have checked on freshly Masakari deployment: the endpoint in Keystone is http:// indeed, and:
# the certs are present: 2d3b82- 0-lxd-10: ~# ls /etc/apache2/ ssl/masakari/
root@juju-
cert_10.35.174.113 cert_10.35.84.244
# but https-related apache conf is empty sites-enabled/ openstack_ https_frontend. conf 2d3b82- 0-lxd-10: ~#
~# cat /etc/apache2/
root@juju-