faa8cb0fb7
900.002 alarm is sometimes raised after install or host unlock on all deploy types. This is an intermittent behaviour that happens because sw-patch is malfunctioning as it is no longer supported and has been replaced by USM. The patch-alarm package provides the patch-alarm-manager service and the alarms raised by patch-alarm-manager are: FM_ALARM_ID_PATCH_IN_PROGRESS = 900.001 FM_ALARM_ID_PATCH_HOST_INSTALL_FAILED = 900.002 FM_ALARM_ID_PATCH_OBS_IN_SYSTEM = 900.003 FM_ALARM_ID_NONSTANDARD_CERT_PATCH = 500.101 Since sw-patch will no longer be supported and the mechanism for raising alarms on patch-alarm depends on the sw-patch endpoints, the 900.002 alarm will be disabled to avoid unexpected behaviour. USM does not have the same patch application mechanisms and some alarms have been implemented already: FM_ALARM_ID_USM_DEPLOY_HOST_SUCCESS_RR = 900.020 FM_ALARM_ID_USM_DEPLOY_HOST_FAILURE = 900.021 TODO: Investigate if the any of the legacy alarms should be adapted to work with USM patching. Test Plan: PASS: Successful AIO-DX deploy with no 900.002 alarm PASS: Multiple lock-unlock operations with no alarms Closes-bug: 2056295 Change-Id: I844311e538aec0bc8990645d6ac0d254cb1e4a3a Signed-off-by: Matheus Guilhermino <Matheus.MachadoGuilhermino@windriver.com> |
||
|---|---|---|
| .. | ||
| patch_alarm | ||
| .coveragerc | ||
| .stestr.conf | ||
| LICENSE | ||
| pylint.rc | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||