Warm reset check fix
There is an intermittent failure report due to false reboot failure
raised by the utility keyword which checks if the SSH service while
BMC is going through reboot.
Warm reset adds 3 seconds delay before forcing reboot. To minimize
race conditions, we wait for 7 seconds and check status.
Any better suggestion on how to workaround this logic is most welcome.
Resolves openbmc/openbmc-test-automation#238
Change-Id: I6f99c1a47aa6d183ae6526463cc897f796ef01fb
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/lib/utils.robot b/lib/utils.robot
index 385183e..cfcbd8f 100755
--- a/lib/utils.robot
+++ b/lib/utils.robot
@@ -281,6 +281,10 @@
[Documentation] Ping would be still alive, so try SSH to connect
... if fails the ports are down indicating reboot
... is in progress
+
+ # Warm reset adds 3 seconds delay before forcing reboot
+ # To minimize race conditions, we wait for 7 seconds
+ Sleep 7s
${alive}= Run Keyword and Return Status
... Open Connection And Log In
Return From Keyword If '${alive}' == '${False}' ${False}