Comment 2 for bug 2004638

Reviewed: https://review.opendev.org/c/starlingx/distcloud/+/872643
Committed: https://opendev.org/starlingx/distcloud/commit/591a06e858526f23ccd85e5a684903d0b0e6d156
Submitter: "Zuul (22348)"
Branch: master

commit 591a06e858526f23ccd85e5a684903d0b0e6d156
Author: Christopher Souza <email address hidden>
Date: Fri Feb 3 07:57:07 2023 -0300

    Clear 280.003 alarm on subcloud deletion

    When a subcloud was deleted, the 280.003 alarm was not cleared.
    The change was to add the 280.003 alarm to the list of alarms that are checked.

    Test Plan:

    PASS: Install and bootstrap DC.
    PASS: create a subcloud backup and power off the subcloud after reaching:
    "Run subcloud1 backup playbook".
    PASS: Wait for the alarm 280.003 to be set, then umanage and
    delete the subcloud and check if the 280.003 alarm was cleared.

    Closes-bug: 2004638

    Signed-off-by: Christopher Souza <email address hidden>
    Change-Id: I70458b1fe6da4b9c0bf458ee57720a4ffaeafbfb