Comment 3 for bug 2032703

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

commit 0c5e6b143965a6b58dcad6de23d67f1d70c58a20
Author: Luan Nunes Utimura <email address hidden>
Date: Tue Aug 22 20:59:20 2023 -0300

    Fix TLS vol. in cinder-volume-usage-audit CronJob

    After the recent upversion of openstack-helm [1], it has been observed
    that the `cinder-volume-usage-audit` pod is having problems booting on
    systems with HTTPS enabled due to a misconfigured TLS-related
    volume/volumeMount pair.

    Apparently, this pair of volume and volumeMount was introduced with the
    upversion of openstack-helm, and ended up being left out of the changes
    made by patch `0010-Remove-TLS-from-openstack-services.patch` that, in
    theory, would have solved the problem.

    Therefore, this change aims to update the patch in question -- along
    with any other patches to avoid conflicts -- so that the
    `cinder-volume-usage-audit` pod no longer has problems booting on
    systems with HTTPS enabled.

    [1] https://opendev.org/starlingx/openstack-armada-app/commit/8254cd31bb1f12eebc48b712b33f75b2fc0aa571

    Test Plan (on AIO-DX with HTTPS enabled):
    PASS - Build openstack-helm package
    PASS - Build stx-openstack-helm-fluxcd package
    PASS - Build stx-openstack helm charts
    PASS - Upload/apply stx-openstack
    PASS - Verify that all pods -- including `cinder-volume-usage-audit` --
           are either "Running" or "Completed"
    PASS - Remove/delete stx-openstack

    Closes-Bug: 2032703

    Change-Id: Ic13c6945cc9e43f9153820297e74623520446fcd
    Signed-off-by: Luan Nunes Utimura <email address hidden>
    (cherry picked from commit be56c15bc043528f4448ae607182d97641fc8766)