Comment 2 for bug 2052550

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/c/starlingx/config/+/908194
Committed: https://opendev.org/starlingx/config/commit/efd42f0ab8e7d1cd7b6f0f2cf7010cb2c7e7be8a
Submitter: "Zuul (22348)"
Branch: master

commit efd42f0ab8e7d1cd7b6f0f2cf7010cb2c7e7be8a
Author: amantri <email address hidden>
Date: Tue Feb 6 14:42:40 2024 -0500

    Raise alarm on secret "sc-adminep-ca-certificate" at subcloud

    When "sc-adminep-ca-certificate" secret falls under alarm-before expiry
    period, the 500.200 expiry alarm is not raised at subcloud as it is
    being filtered out, this fix will do filtering only on systemcontroller
    and raising the alarm at subcloud.

    Test Cases:
    PASS: Change "<subcloudid>-adminep-ca-certificate" at systemcontroller
          so that it falls under the alarm-before timeline, notice
          cert-mon updates the "sc-adminep-ca-certificate" secret at
          subcloud and raises the 500.200 expiry alarm at subcloud.
          Verify no alarm is raised for secret
          "<subcloudid>-adminep-ca-certificate" at systemcontroller
    PASS: On standalone, verify that cert-alarm raises expiry alarms
          without any issues

    Closes-bug: 2052550

    Change-Id: I03c475bc72b1d8212b185935db956275284674ec
    Signed-off-by: amantri <email address hidden>