Wait for iDRAC reset fails
Bug #1816195 reported by
Christopher Dearborn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-dracclient |
Fix Released
|
High
|
Christopher Dearborn |
Bug Description
The current iDRAC reset code waits for 3 consecutive failed pings, each 10 seconds apart to determine that an iDRAC has gone down. 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.
We need to reduce the number of consecutive failed pings to 2, which we have tested extensively downstream.
Changed in python-dracclient: | |
assignee: | nobody → Christopher Dearborn (cdearbor) |
importance: | Undecided → High |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/637288 /git.openstack. org/cgit/ openstack/ python- dracclient/ commit/ ?id=e204c367ab1 18878aa5202e10d 74c3c28de8ba21
Committed: https:/
Submitter: Zuul
Branch: master
commit e204c367ab11887 8aa5202e10d74c3 c28de8ba21
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
Change-Id: Iac21d5eb722834