commit 68cbf5a06ebaf505096e71041d24e01d95b266b3
Author: Christopher Dearborn <email address hidden>
Date: Fri Feb 15 14:54:25 2019 -0500
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)
Reviewed: https:/ /review. opendev. org/650104 /git.openstack. org/cgit/ openstack/ python- dracclient/ commit/ ?id=68cbf5a06eb af505096e71041d 24e01d95b266b3
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 68cbf5a06ebaf50 5096e71041d24e0 1d95b266b3
Author: Christopher Dearborn <email address hidden>
Date: Fri Feb 15 14:54:25 2019 -0500
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 089cbe4a2e7e193 70a951951f0 8aa5202e10d74c3 c28de8ba21)
Change-Id: Iac21d5eb722834
(cherry picked from commit e204c367ab11887