Host in degraded state with no alarm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Eric MacDonald |
Bug Description
If the starlingx collectd memory, cpu or filesystem usage plugin asserts a critical alarm that causes degrade and somehow that alarm is lost or manually deleted then the host can get into a state where it is degraded with no alarm.
Severity: Minor - requires manual action or an upgrade that drops the fm database to occur.
Steps to Reproduce: Delete a critical 100.101, 100,103 or 100.104 alarm
Expected Behavior: Alarm gets recreated
Actual Behavior: Host is degraded with no alarm
Reproducibility : 100% in the unlikely case this does occur.
System Configuration: Any
Branch/Pull Time/Commit: Any as of April 2021
Last Pass: Not tested
Timestamp/Logs
--------------
2021-04-
2021-04-
Test Activity: Feature Testing
Workaround: Restart collectd
Changed in starlingx: | |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /monitoring/ +/787202
Review: https:/