250.001 alarm raised and not clearing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Medium
|
Kristine Bujold |
Bug Description
Brief Description
-----------------
Alarm "Configuration is out-of-date" is not clearing even after lock/unlock operation on single host (controller/worker)
Severity
--------
Minor
Steps to Reproduce
------------------
The testcase creates flavors, launches instances on the controller/worker
Reboots the host with reboot -f command
Waits for reboot to succeed and state to reach:
['controller-0'] have reached state(s): {'availability': ['available', 'degraded']}
Note: The alarm was raised @ 2020-01-
The test then deletes the instances and flavors that were created and checks the alarms.
300 seconds later @ [2020-01-15 16:18:13,883] the 250.001 alarm is still there
Expected Behavior
------------------
The alarm "Configuration is out-of-date" should be cleared but does not
Actual Behavior
----------------
The alarm "Configuration is out-of-date" (250.001) is not cleared ever (even after lock/unlock operation)
Reproducibility
---------------
yes
(failed teardown in test
nova/test_
System Configuration
-------
tested on
single node system
Branch/Pull Time/Commit
-------
20200111T023000Z
Last Pass
---------
Timestamp/Logs
--------------
see Fm-manager.log when the alarm first appears
2020-01-
2020-01-
2020-01-
see Fm-manager.log after lock/unlock attempt
2020-01-
2020-01-
Test Activity
-------------
LP retest
Workaround
----------
tags: | added: stx.retestneeded |
tags: | added: stx.4.0 |
tags: | removed: stx.retestneeded |
lab: SM-2