Bug 726772

Summary: cman and ccs packages contain different cluster.rng schema files for RHEL 6.3 Cluster
Product: Red Hat Enterprise Linux 6 Reporter: Aleksandr Brezhnev <brezhnev>
Component: ricciAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1CC: ccaulfie, cluster-maint, lhh, rpeterso, rsteiger, syeghiay, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ricci-0.16.2-55.el6 Doc Type: Bug Fix
Doc Text:
Cause: a different cluster schema is on a node vs. what's provided in ccs Consequence: A cluster.conf file that is valid on the node may be interpreted as invalid by ccs Fix: a --getschema command was added and ccs will now use the node cluster schema to do verification Result: When cluster schemas are different between what is included with ccs and what is on a node, the cluster schema on the node is used.
Story Points: ---
Clone Of:
: 801051 (view as bug list) Environment:
Last Closed: 2012-06-20 14:13:18 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: 794907, 797267    
Bug Blocks: 756082    

Description Aleksandr Brezhnev 2011-07-29 18:49:27 UTC
Description of problem:

The cman and ccs packages in RHEL6.1 Cluster use different cluster schemas.

Version-Release number of selected component (if applicable):
cman-3.0.12-41.el6.x86_64
ccs-0.16.2-35.el6.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Identify cluster.rng files: 
rpm -ql cman | grep cluster.rng
/usr/share/cluster/cluster.rng

rpm -ql ccs | grep cluster.rng
/usr/share/ccs/cluster.rng

2. Compare them.
md5sum /usr/share/cluster/cluster.rng /usr/share/ccs/cluster.rng
4b95c0a674eea33fc49009e7d87037c9  /usr/share/cluster/cluster.rng
786fc0ec6a3d605507b65922739501f5  /usr/share/ccs/cluster.rng
  
Actual results:
The files are different

Expected results:
The files should be the same

Additional info:

Comment 7 Chris Feist 2012-02-27 23:27:48 UTC
Fixed here:

https://github.com/feist/ccs/commit/f8884fa4ef9bf30f09d27098d6a8d3925fb6afe3

Before Fix:
ccs -h ask-03 --getschema

... prints usage ...

After Fix:

... prints schema ...

Comment 8 Chris Feist 2012-02-28 02:24:08 UTC
With ricci-0.16.2-48.el6

[root@ask-04 ~]# ccs -h localhost --getschema | tail
<optional>
<empty/>
</optional>
</group>
<!-- end specific fence devices -->
</choice>
</optional>
</define>
<!-- end fence attribute group definitions -->
</grammar>

Comment 10 Chris Feist 2012-03-15 19:55:50 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: a different cluster schema is on a node vs. what's provided in ccs

Consequence: A cluster.conf file that is valid on the node may be interpreted as invalid by ccs

Fix: a --getschema command was added and ccs will now use the node cluster schema to do verification

Result: When cluster schemas are different between what is included with ccs and what is on a node, the cluster schema on the node is used.

Comment 17 Chris Feist 2012-05-02 00:07:32 UTC
Before Fix:


[root@localhost ~]# rpm -q fence-agents resource-agents ccs
fence-agents-3.1.5-17.el6.x86_64
resource-agents-3.9.2-12.el6.x86_64
ccs-0.16.2-54.el6.x86_64
[root@localhost ~]# diff -q /usr/share/ccs/cluster.rng /var/lib/cluster/cluster.rng 
Files /usr/share/ccs/cluster.rng and /var/lib/cluster/cluster.rng differ

After Fix:

[root@localhost ~]# rpm -Uvh ccs-0.16.2-55.el6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:ccs                    ########################################### [100%]
[root@localhost ~]# diff -q /usr/share/ccs/cluster.rng /var/lib/cluster/cluster.rng
[root@localhost ~]#

Comment 20 errata-xmlrpc 2012-06-20 14:13:18 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-0898.html