Description of problem: When creating a load balancer through Horizon, the TERMINATED_HTTPS listener type is greyed out. This is due to a 404 when hitting /dashboard/api/barbican/certificates. Version-Release number of selected component (if applicable): OSP13 RC How reproducible: Deploy an OSP13 overcloud with Ocatvia and Barbican. Attempt to create a load balancer through the Horizon UI and note that the TERMINATED_HTTPS listener type is not available and your browser reports 404 responses from the octavia_horizon Barbican APIs. Actual results: TERMINATED_HTTPS is greyed out Expected results: TERMINATED_HTTPS should be selectable and certificates should appear in the UI Additional info: The return from the octavia_horizon Barbican API indicates that the Keystone URL is malformed. Adding /v3 to the Keystone URL in the Horizon configuration results in the expected behavior.
Horizon will automatically add the /v3 at the end if it's missing, so it seems like the octavia plugin is not using horizon's mechanisms here, but instead doing something weird on their own?
I can reproduce this in latest OSP 13. I will be working on a fix in the coming days. Thanks to Radomir for the help troubleshooting and pointing me in the right direction to a fix.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0926