tree 4748f29cdb1b4b983935554f9d59e168ce48c2c1
parent b821c51b7bf39ad5a4df329c1073dcc52640cf7d
author Tim Lee <timlee660101@gmail.com> 1650957047 +0800
committer George Keishing <gkeishin@gmail.com> 1651038121 +0000

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