Browse Source

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 e204c367ab)
changes/91/645291/1
Christopher Dearborn 3 years ago
parent
commit
b1b49fb482
  1. 2
      dracclient/client.py

2
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:

Loading…
Cancel
Save