2ef6c9524c
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 <andy.ning@windriver.com> Change-Id: I82b922f39d185990704c591f02781d581822b162 |
||
---|---|---|
.. | ||
controllers | ||
middleware | ||
__init__.py | ||
acl.py | ||
app.py | ||
config.py | ||
hooks.py |