remove stale backup in progress alarm 210.001

[ramu ummadishetty]

Brief Description
-----------------
user is unable to backup subcloud when there is a stale backup in progress alarm

Severity
--------
Provide the severity of the defect.
Minor: this is affecting the user in subsequent backup

Steps to Reproduce
------------------
raise a dummy 210.001 alarm in one of the managed subcloud and try to take that paricular subcloud backup using dcmanger cmd

Expected Behavior
------------------
usually subcloud backup should not take more than 1 hour

Actual Behavior
----------------
there should not be any stale backup in progress alarms which is management affecting.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
Distributed Cloud

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/913953

[OpenStack Infra (hudson-openstack)]

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

commit a3a20fcf59174c8891d22bd396c3a589e9987172
Author: rummadis <email address hidden>
Date: Fri Mar 22 03:14:27 2024 -0400

    Prune stale backup in progress alarm 210.001

    User unable to take subcloud backup when there
    is a stale backup in progress alarm

    Example:
    When user tries to take subcloud backup in
    Distributed cloud env if there is stale
    210.001 alarm present in subcloud then user
    can not trigger the subsequent subcloud backup

    This Fix helps to identify the 210.001 alarms
    and clear them if they are pending more than 1
    hour

    TEST PLAN:
    PASS: DC-libvirt setup with 2 controllers
    and 2 subclouds
    PASS: verified stale 210.001 getting removed

    Closes-Bug: 2058516

    Change-Id: Iedcc5e41cd4245c538d331d9aa8c2b6cc445acce
    Signed-off-by: rummadis <email address hidden>