StarlingX Fault Management
4246a0448d
Doing filesystem resizes is blocked when a node is degraded and going over 90% filesystem utilization degrades the node. This prevents the user from clearing the alarm by resizing and adding more space to a certain filesystem. To fix this, we check add a new field to every alarm marking which alarm causes a degrade. In case of a filesystem resize, we poll all alarms and filter them for those that are causing a degrade. If the only alarm that causes a degrade is the filesystem usage alarm, then it is safe to proceed with the resize. Change-Id: I9b4a9c34f625ef2669725d489460b15e637c1efc Signed-off-by: Jack Ding <jack.ding@windriver.com> |
||
---|---|---|
fm-api | ||
fm-common | ||
fm-doc | ||
fm-mgr | ||
snmp-audittrail | ||
snmp-ext | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
centos_pkg_dirs | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
mwa-cleo.map | ||
README.rst | ||
test-requirements.txt | ||
tox.ini |
stx-fault
StarlingX Fault Management