Bug 172177 - clustat -x output is missing current/last owner
clustat -x output is missing current/last owner
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: rgmanager (Show other bugs)
4
All Linux
medium Severity high
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-31 23:00 EST by Jiho Hahm
Modified: 2009-04-16 16:18 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2006-0173
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-01-06 15:22:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Fixes behavior (836 bytes, patch)
2005-11-01 09:58 EST, Lon Hohberger
no flags Details | Diff

  None (edit)
Description Jiho Hahm 2005-10-31 23:00:54 EST
Description of problem:

clustat -x output always shows "(null)" or "none" for "owner" and "last_owner"
attributes.  The non-XML output of clustat reports the correct information. 
However, I need the XML output to integrate cluster status into my own
administration interface.  Because of the bug I have no way of knowing on which
cluster members the services are running.


Version-Release number of selected component (if applicable):

    rgmanager-1.9.39-0
    Problem did not happen in the previous release, 1.9.38-0.


How reproducible:


Steps to Reproduce:
1. Run "clustat"
2. Run "clustat -x"
3. Compare the results.
  
Actual results:

owner and last_owner attributes of <group> element is always "(null)" or "none"
while the non-XML clustat output shows the right data.

Expected results:


Additional info:

It looks like non-XML clustat output was improved to show which member is local
member and whether rgmanager is running.  This data should be returned in the
XML output as well.

The correct owner should be returned for "starting" status as well as "started",
so that a custom <script> resource can tell in which service's context it is
being invoked.
Comment 1 Lon Hohberger 2005-11-01 09:58:51 EST
Created attachment 120603 [details]
Fixes behavior
Comment 2 Jiho Hahm 2005-11-01 13:33:19 EST
The patch works.  Thanks for the quick response.
Comment 5 Red Hat Bugzilla 2006-01-06 15:22:52 EST
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-2006-0173.html

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