From b1b49fb48223e10863e1584c61ba8dfac26bd9d3 Mon Sep 17 00:00:00 2001 From: Christopher Dearborn Date: Fri, 15 Feb 2019 14:54:25 -0500 Subject: [PATCH] Fix iDRAC reset The current code waits for 3 consecutive failed pings, each 10 seconds apart to determine that an iDRAC has gone down during an iDRAC reset. This is too long for some servers, as the iDRAC may come back up before the 3rd ping failure. This results in a failure to detect the iDRAC going down, which causes a timeout on the reset. This patch changes the code to wait for only 2 consecutive ping failures, which is what our highly tested downstream code does. Closes-Bug: 1816195 Change-Id: Iac21d5eb722834089cbe4a2e7e19370a951951f0 (cherry picked from commit e204c367ab118878aa5202e10d74c3c28de8ba21) --- dracclient/client.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dracclient/client.py b/dracclient/client.py index 74decc3..b70abb4 100644 --- a/dracclient/client.py +++ b/dracclient/client.py @@ -272,7 +272,7 @@ class DRACClient(object): state_reached = self._wait_for_host_state( self.client.host, alive=False, - ping_count=3, + ping_count=2, retries=24) if not state_reached: