systems: eventlog: fix Host state cannot match expected match_state
Symptom:
Boot failures exceed the boot failure threshold. The states no longer match.
state:
[boot_progress]: Unspecified
[host]: Running
[operating_system]: Inactive
match_state:
[boot_progress]: FW Progress, Starting OS|OSStart
[operating_system]: Standby
[host]: Running
Root cause:
In test "test_event_logging.robot" that use "Trigger Host Watchdog Error" cause
Host be rebooted by watchdog. However, in "test_led_indicator_asserted.robot"
that will call "Redfish Power ${pre_req_state}" to keep Host at previous state
then perform the test. Sometimes, this results the host report is not be booted
even if it actually is. Eventually, cause test case confusion then return error
Solution:
For fixing this false alarm wait few seconds for Host be booted properly
Tested:
Run robot test redfish/systems/eventlog/test_event_logging.robot then
run redfish/systems/test_led_indicator_asserted.robot continuity
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I2f7e93df9b430cc889d8f0b09ac86b9acaf039df
diff --git a/redfish/systems/eventlog/test_event_logging.robot b/redfish/systems/eventlog/test_event_logging.robot
index 17cf112..342112e 100644
--- a/redfish/systems/eventlog/test_event_logging.robot
+++ b/redfish/systems/eventlog/test_event_logging.robot
@@ -359,6 +359,13 @@
Wait Until Keyword Succeeds 2 min 30 sec
... Verify Watchdog EventLog Content
+ ${running_states}= Create Dictionary
+ ... bmc=Enabled
+ ... chassis=On
+ ... host=Enabled
+ ... boot_progress=OSBootStarted
+
+ Wait Until Keyword Succeeds 1 min 10 sec Match State ${running_states}
Verify Event Logs Capping
[Documentation] Verify event logs capping.