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.

Description of problem:
Luci only talks to ricci on one node of the cluster, if that node's cluster infrastructure is stopped (service cman stop), luci will continue using that node and erroneously report that there is no cluster formed.

Version-Release number of selected component (if applicable):
luci-0.22.2-2.el6

How reproducible:
Everytime

Steps to Reproduce:
1. Create/Add a 2 node cluster 
2. Stop ricci on first node
3. Hit refresh in the luci interface 3 times
4. start ricci on the first node
5. Run 'service cman stop' on the second node
6. Refresh the luci interface 3 times, both nodes will appear to be not members of the cluster.
7. Login to the 1st node and run 'cman_tool status', you will see that the cluster is still in fact running and that the 1st node is a member of the cluster.

  
Actual results:
Cluster appears to be down from luci interface

Expected results:
Luci should show that the cluster is working but the second node is not part of the cluster

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

*** Bug 616377 has been marked as a duplicate of this bug. ***

Created attachment 436426 [details]
fix node communication through modclusterd

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.