Bug 856785 - luci misses real state of services due to inactive modclusterd at the nodes [NEEDINFO]
luci misses real state of services due to inactive modclusterd at the nodes
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Ryan McCabe
Depends On:
  Show dependency treegraph
Reported: 2012-09-12 15:25 EDT by Jan Pokorný
Modified: 2015-10-14 17:08 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-14 17:08:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rsteiger: needinfo? (jpokorny)

Attachments (Terms of Use)

  None (edit)
Description Jan Pokorný 2012-09-12 15:25:19 EDT
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

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

Note You need to log in before you can comment on or make changes to this bug.