Red Hat Bugzilla – Bug 150346
clustat is riddled with usability problems
Last modified: 2009-04-16 16:16:48 EDT
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".
Furthermore, there isn't enough space for all the service states in the service state column. recovering works, but "uninitialized", etc. don't. e.g.: uninitiali recoverabl
... And "resource groups" aren't the right name, they're "Services"
*** Bug 158611 has been marked as a duplicate of this bug. ***
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
Fix in CVS.
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. http://rhn.redhat.com/errata/RHBA-2005-821.html