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.

I was able to reproduce the situation discussed in linux-cluster ML [1].
Briefly: luci keeps showing a service as disabled, which is contrary to
what clustat correctly indicates (e.g., service is started).

The cause (at least in my case) was modclusterd not running on any node,
especially not on the node currently selected by luci as a main source
of information.

Ways leading to this state are to be examined, but generally, if you
do not create cluster via luci with "Download Packages" option selected
(non-default), you do not have any daemon (incl. modclusterd) started
automatically.

For modclusterd, this situation is partially captured by starting it
automatically upon any cluster-related request against ricci.  However,
usually the only node is being used for fetching cluster status, so
this mechanism is likely not to be 100%.

[1] https://www.redhat.com/archives/linux-cluster/2012-September/msg00047.html

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days