Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 546340

Summary: LOGIN_TIMEOUT too short for fence_lpar
Product: Red Hat Enterprise Linux 5 Reporter: Matt Brodeur <mbrodeur>
Component: cmanAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4.zCC: cluster-maint, djansa, edamato, jkortus
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: cman-2.0.015-25-el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:41:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matt Brodeur 2009-12-10 17:06:48 UTC
Description of problem:
When using fence_lpar against our v7 HMC in RDU the SSH login times out before the connection can be completed.  The timeout in fencing.py is 5 seconds, and it takes up to 10 for the HMC to respond.


Version-Release number of selected component (if applicable):
cman-2.0.115-1.el5_4.9

How reproducible:
100%

Additional info:
The error returned is "Unable to connect/login to fencing device" (EC_LOGIN_DENIED) instead of the more helpful "Connection timed out" (EC_TIMED_OUT).  Setting "LOGIN_TIMEOUT = 15" in /usr/lib/fence/fencing.py solves the problem, at least in our limited tests.

Comment 1 Marek Grac 2009-12-14 14:28:14 UTC
In next version there will be an option --login-timeout which can be used to set it directly. I will set your value (15) as default for LPAR fence agent.

Comment 6 errata-xmlrpc 2010-03-30 08:41:58 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0266.html