Comment 5 for bug 1949238

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

commit 2ef6c9524c5346547872959c68f7741a9c13b280
Author: Andy Ning <email address hidden>
Date: Tue Nov 23 13:40:59 2021 -0500

    Remove force option for k8s rootca update complete/abort

    Currently the k8s rootca update complete and abort will be rejected
    if system has alarms that are not ignored internally. "-f" option
    can be used to suppress none mgmt_affecting alarms, but mgmt_affecting
    alarms will still prevent complete and abort.

    Blocking complete and abort by alarms is not really neccessary since
    it won't help user to solve the alarms anyway, and at the same time
    causes confusion to the end users.

    This update remove alarm checking (and the -force option) from REST
    API and system CLI.

    Test Plan:
    PASS: rootca update complete while system has alarm
    PASS: rootca update abort at host-update trust-both-cas while system
          has alarms
    PASS: rootca update abort at host-update update-certs while system
          has alarms
    PASS: rootca update abort at host-update trust-new-ca while system
          has alarms
    PASS: rootca update abort at pods-update trust-both-cas while system
          has alarms

    Closes-Bug: 1949238
    Signed-off-by: Andy Ning <email address hidden>
    Change-Id: I82b922f39d185990704c591f02781d581822b162