Wait for iDRAC reset fails

[Christopher Dearborn]

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.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/637288
Committed: https://git.openstack.org/cgit/openstack/python-dracclient/commit/?id=e204c367ab118878aa5202e10d74c3c28de8ba21
Submitter: Zuul
Branch: master

commit e204c367ab118878aa5202e10d74c3c28de8ba21
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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/645291

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/645291
Committed: https://git.openstack.org/cgit/openstack/python-dracclient/commit/?id=b1b49fb48223e10863e1584c61ba8dfac26bd9d3
Submitter: Zuul
Branch: stable/queens

commit b1b49fb48223e10863e1584c61ba8dfac26bd9d3
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)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650104

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/650104
Committed: https://git.openstack.org/cgit/openstack/python-dracclient/commit/?id=68cbf5a06ebaf505096e71041d24e01d95b266b3
Submitter: Zuul
Branch: stable/stein

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)