Bug 150346 - clustat is riddled with usability problems
clustat is riddled with usability problems
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: rgmanager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
: 158611 (view as bug list)
Depends On: 157098
  Show dependency treegraph
Reported: 2005-03-04 14:27 EST by Lon Hohberger
Modified: 2009-04-16 16:16 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2005-821
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-28 16:01:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lon Hohberger 2005-03-04 14:27:32 EST
Description of problem:

The output of clustat when the node is or isn't running rgmanager is
completely different.  Also, the output is completely bogus when
running GuLM -- it reports all nodes as members of any given group.

This is partly a magma-ism:  Magma reports that all nodes are members
of all requested groups irrespective of the infrastructure's support
of "node groups" or "service groups".
Comment 1 Lon Hohberger 2005-03-07 12:24:37 EST
Furthermore, there isn't enough space for all the service states in
the service state column.

recovering works, but "uninitialized", etc. don't.


Comment 2 Lon Hohberger 2005-05-06 16:35:26 EDT
... And "resource groups" aren't the right name, they're "Services"
Comment 3 Lon Hohberger 2005-05-23 19:18:37 EDT
*** Bug 158611 has been marked as a duplicate of this bug. ***
Comment 4 Lon Hohberger 2005-05-24 16:53:04 EDT
Considering changing (as an example) to the following output format for clustat.
 This would require a rewrite; as it would require CCS information which is
currently not needed.

Node flags:

R = "running rgmanager" - member of the rgmanager service group (cman only)
L = "local node": replaces the "<--- You are here" indicator
M = Missing from ccs configuration!

Service flags:

N = "No-autostart" Autostart disabled (service starts automatically when cluster
is quorate)
X = Exclusive service

Output when running on a node running rgmanager (example only):

  Member Name                              State      Flags
  ------ ----                              -----      -----
  red                                      Online     RL
  green                                    Online     R
  blue                                     Offline
  cyan                                     Online     M
  magenta                                  Online     R

  Service Name         Owner (Last)        State      Flags     
  ------- ----         ----- ------        -----      -----
  nfsservice           red                 started    
  redonly              red                 started   
  greenonly            (none)              stopped    N
  nostart              (none)              stopped    NX
  exclusive            (none)              stopped    X
  greenpref            red                 started  

Output on a node not running rgmanager:

Not running rgmanager.  Service state information unavailable.

  Member Name                              State      Flags
  ------ ----                              -----      -----
  red                                      Online     L
  green                                    Online     
  blue                                     Offline
  cyan                                     Online     M
  magenta                                  Online
Comment 5 Lon Hohberger 2005-10-17 16:34:37 EDT
Fix in CVS.
Comment 7 Red Hat Bugzilla 2005-10-28 16:01:34 EDT
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 the 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.


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