Brute force power on for watchdog timedout test
Resolves openbmc/openbmc-test-automation#858
Change-Id: I6a355cf0c52e352edc24356146f02ea64c61a3d6
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/tests/test_error_log.robot b/tests/test_error_log.robot
index c78221e..db72112 100644
--- a/tests/test_error_log.robot
+++ b/tests/test_error_log.robot
@@ -230,15 +230,12 @@
[Documentation] Trigger watchdog timed out and verify errorlog generated.
[Tags] Verify_Watchdog_Timedout_Error
+ REST Power Off
+ REST Power On
+
# Clear errors if there are any.
Delete Error Logs
- Initiate Host Boot
-
- # Check if the watchdog interface is created.
- Wait Until Keyword Succeeds 3 min 10 sec
- ... Read Properties /xyz/openbmc_project/watchdog/host0
-
Trigger Host Watchdog Error
Verify Watchdog Errorlog Content
@@ -443,7 +440,7 @@
[Documentation] Delete all error logs and verify.
Delete Error Logs
- ${resp}= OpenBMC Get Request ${BMC_LOGGING_ENTRY}/list
+ ${resp}= OpenBMC Get Request ${BMC_LOGGING_ENTRY}/list quiet=${1}
Should Be Equal As Strings ${resp.status_code} ${HTTP_NOT_FOUND}
Post Test Case Execution