Stuck host configuration failure alarm (200.011)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Eric MacDonald |
Bug Description
AIO SX experienced a Configuration Failure that raised 200.011 alarm.
Since system type is AIO SX the failure lead to degrade rather than failure of only controller.
The Configuration Failure lead to a persistent quorum process (mtcClient) failure and self reboot.
Controller-0 came up over reboot with a valid config but mtcAgent did not clear the config alarm
Severity
--------
Minor: Issue requires config failure to occur followed by a system reset that corrects the configuration issue. Unlikely, is only a stuck alarm and there is a work around.
Steps to Reproduce
------------------
Create configuration failure until alarm 200.011 is raised.
reboot host where it recovers with no configuration failure.
Expected Behavior
------------------
no stuck 200.011 alarm
Actual Behavior
----------------
stuck 200.011 alarm
Reproducibility
---------------
100% with above conditions met.
System Configuration
-------
AIO SX or more generally a Simplex system
Branch/Pull Time/Commit
-------
March 2021
Last Pass
---------
Test Escape
Timestamp/Logs
--------------
N/A
Test Activity
-------------
[Other]
Workaround
----------
Lock/Unlock controller-0
low priority - minor issue w/ existing workaround