Bug 794907

Summary: modcluster doesn't properly return the cluster schema
Product: Red Hat Enterprise Linux 6 Reporter: Chris Feist <cfeist>
Component: clustermonAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: cluster-maint, rsteiger
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: modcluster-0.16.2-18.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 797267 (view as bug list) Environment:
Last Closed: 2012-06-20 11:57:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 726772, 797267    

Description Chris Feist 2012-02-17 21:45:30 UTC
When asking clustermon for the cluster schema it mangles the schema so we can't use it for xmllint.

For example:
The original cluster.rng file has some of this info:


<start>
<element name="cluster" rha:description="Defines cluster properties, and
    contains all other configuration. cluster.conf(5)">

when pulling that from clustermon I see this output from the same section:

<start>
<element description="Defines cluster properties, and     contains all other configuration. cluster.conf(5)" name="cluster">

clustermon should return the exact (or possibly re-formatted with tabs/spaces) cluster.rng that is on the server.

Comment 1 Ryan McCabe 2012-02-21 18:11:33 UTC
This would have to be fixed in both ricci and clustermon. The code that mangles the XML like this is XMLObject that both ricci and clustermon share. ricci will re-mangle proper output from clustermon when it reads it from the batch files.

Comment 2 Ryan McCabe 2012-02-21 18:13:24 UTC
^^ or from stdout

Comment 9 errata-xmlrpc 2012-06-20 11:57:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0750.html