STX-OPenstack: Unable to retrieve images via Horizon when HTTPS is enabled

[Lucas de Ataides Barreto]

Brief Description
-----------------
When trying to create a VM in STX-Openstack in a lab environment that HTTPS certificate enabled, the images are not being retrieved through glance in Horizon

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
1. Install lab with https enabled
2. upload image via glance
3. try to access the images in horizon (admin -> compute -> images)

Expected Behavior
------------------
The images should be listed

Actual Behavior
----------------
The images are not listed

Reproducibility
---------------
Seen once

System Configuration
--------------------
Baremetal AIO-DX

Branch/Pull Time/Commit
-----------------------
20230822T060000Z

Last Pass
---------
https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014447.html - 20230820T060000Z

Test Activity
-------------
Feature Testing

Workaround
----------
N/A

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/openstack-armada-app/+/892707

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/openstack-armada-app/+/892707
Committed: https://opendev.org/starlingx/openstack-armada-app/commit/efd6f74d40762afeebefad17b2e59626403e8eb3
Submitter: "Zuul (22348)"
Branch: master

commit efd6f74d40762afeebefad17b2e59626403e8eb3
Author: Lucas de Ataides <email address hidden>
Date: Thu Aug 24 15:37:52 2023 -0300

    Update Horizon SSL Cert path

    It was observed that, when using the STX-Openstack app with HTTPS
    enabled, it was not possible to visualize / edit / create images using
    Horizon. This was caused because the SSL certificate (ca.crt) volume
    mount path defined in Horizon's configuration [1] was not the same as
    the default one created when using the Helm toolkit [2].

    As specified in [3], one possible solution was to define a path to the
    TLS secret to be created, but that caused other services in Horizon to
    fail, so instead of doing that, the solution was to change Horizon's
    configuration to search the ca.crt file in the correct path.

    [1] https://opendev.org/openstack/openstack-helm/src/branch/master/horizon/values.yaml#L469
    [2] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/helm-toolkit/templates/snippets/_tls_volume_mount.tpl#L56
    [3] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/helm-toolkit/templates/snippets/_tls_volume_mount.tpl#L30

    Test Plan:
    PASS: Build openstack-helm and stx-openstack-helm-fluxcd
    PASS: Build STX-Openstack tarball
    PASS: Upload / apply STX-Openstack with HTTPS enabled
    PASS: Create an image by using the Glance CLI
    PASS: On Horizon, under Project -> Compute -> Images, verify that the
          image is present
    PASS: Create an image via Horizon

    Closes-Bug: 2032980

    Change-Id: If34c0d4a287804e4fce0e5f70bb97feb330be174
    Signed-off-by: Lucas de Ataides <email address hidden>

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: f/antelope
Review: https://review.opendev.org/c/starlingx/openstack-armada-app/+/892867

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Lucas de Ataides Barreto <email address hidden>" on branch: f/antelope
Review: https://review.opendev.org/c/starlingx/openstack-armada-app/+/892867
Reason: Need to wait for https://review.opendev.org/c/starlingx/openstack-armada-app/+/892587 before opening this cherry pick

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/openstack-armada-app/+/892867
Committed: https://opendev.org/starlingx/openstack-armada-app/commit/d42dd0715916be4d1c2a8f777d752c8c3d2ef43e
Submitter: "Zuul (22348)"
Branch: f/antelope

commit d42dd0715916be4d1c2a8f777d752c8c3d2ef43e
Author: Lucas de Ataides <email address hidden>
Date: Thu Aug 24 15:37:52 2023 -0300

    Update Horizon SSL Cert path

    It was observed that, when using the STX-Openstack app with HTTPS
    enabled, it was not possible to visualize / edit / create images using
    Horizon. This was caused because the SSL certificate (ca.crt) volume
    mount path defined in Horizon's configuration [1] was not the same as
    the default one created when using the Helm toolkit [2].

    As specified in [3], one possible solution was to define a path to the
    TLS secret to be created, but that caused other services in Horizon to
    fail, so instead of doing that, the solution was to change Horizon's
    configuration to search the ca.crt file in the correct path.

    [1] https://opendev.org/openstack/openstack-helm/src/branch/master/horizon/values.yaml#L469
    [2] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/helm-toolkit/templates/snippets/_tls_volume_mount.tpl#L56
    [3] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/helm-toolkit/templates/snippets/_tls_volume_mount.tpl#L30

    Test Plan:
    PASS: Build openstack-helm and stx-openstack-helm-fluxcd
    PASS: Build STX-Openstack tarball
    PASS: Upload / apply STX-Openstack with HTTPS enabled
    PASS: Create an image by using the Glance CLI
    PASS: On Horizon, under Project -> Compute -> Images, verify that the
          image is present
    PASS: Create an image via Horizon

    Closes-Bug: 2032980

    Change-Id: If34c0d4a287804e4fce0e5f70bb97feb330be174
    Signed-off-by: Lucas de Ataides <email address hidden>
    (cherry picked from commit efd6f74d40762afeebefad17b2e59626403e8eb3)