Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 615871

Summary: luci very slow to timeout if a cluster is unreachable
Product: Red Hat Enterprise Linux 6 Reporter: Fabio Massimo Di Nitto <fdinitto>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: bbrock, cluster-maint
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-04 14:23:50 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:
Bug Depends On: 643523    
Bug Blocks:    

Description Fabio Massimo Di Nitto 2010-07-19 07:29:35 UTC
do the usual steps up to configure a cluster properly.

1) stop luci
2) stop the cluster manually
3) remove and reinstall ricci (generates new certs and everything, but no new passwords, those stay the same)
4) start luci
5) access luci

it will take a very long time to report the cluster offline or in an unknown state.

several errors for each node:

09:27:09,476 ERROR [luci.lib.db_helpers] Error communicating with ricci agent at rhel6-node8:11111: Unable to establish an SSL connection to rhel6-node8:11111: timed out
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/luci/lib/db_helpers.py", line 83, in get_agent_for_cluster
    rc = RicciCommunicator(host, port)
  File "/usr/lib/python2.6/site-packages/luci/lib/ricci_communicator.py", line 68, in __init__
    raise RicciError, errmsg
RicciError: Unable to establish an SSL connection to rhel6-node8:11111: timed out
09:27:09,476 ERROR [luci.lib.db_helpers] Unable to communicate with ricci on any nodes in cluster fabbione

Comment 2 RHEL Program Management 2010-07-19 07:58:05 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Fabio Massimo Di Nitto 2010-07-19 08:18:04 UTC
forgot to mention, this is using the latest code from luci.git

Comment 8 Ryan McCabe 2011-02-04 14:23:50 UTC

*** This bug has been marked as a duplicate of bug 643523 ***