This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 210611 - xmllint fails in system-config-cluster
xmllint fails in system-config-cluster
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ryan McCabe
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-13 06:15 EDT by Jos Vos
Modified: 2012-11-07 15:31 EST (History)
2 users (show)

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


Attachments (Terms of Use)
cluster.conf file causing Relax-NG validation errors (1.22 KB, text/plain)
2006-10-13 09:32 EDT, Jos Vos
no flags Details

  None (edit)
Description Jos Vos 2006-10-13 06:15:57 EDT
Description of problem:
Since version 1.0.27-1.0, system-config-cluster runs xmllint to validate the
cluster.conf against a Relax-NG scheme.  This always fails, for both existing
configurations and for newly created configurations with this version.

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

How reproducible:
Create a configuration, save it, and restart system-config-cluster.

Solution:
Fix the Relax-NG scheme or put back the "return" as first statement in the
check_xml() function in CommandHandler.py, as it existed in previous versions.
Comment 1 Jim Parsons 2006-10-13 08:47:36 EDT
Keeping the relax ng file current with additions to the cluster schema is a
challenging job. In addition, the xmllint relaxng checker has its own
challenging issues :) Could you please attach a copy of the cluster.conf that is
failing? Please XXX out your passwords, but leave the structure intact and I
will be able to improve the relaxng file from your example.

BTW, the return statement you refer to above was a debug statement that was
inadvertently left in one release cycle when the conf schema went through alot
of changes. 
Comment 2 Jos Vos 2006-10-13 09:32:02 EDT
Created attachment 138430 [details]
cluster.conf file causing Relax-NG validation errors

With this cluster.conf file, created from scratch and mostly with dummy values,
I get the following errors:

/etc/cluster/cluster.conf:20: element cman: Relax-NG validity error : Expecting
element gulm, got cman
Relax-NG validity error : Extra element fencedevices in interleave
/etc/cluster/cluster.conf:2: element cluster: Relax-NG validity error : Element
cluster failed to validate content
/etc/cluster/cluster.conf fails to validate

The error showed up after adding the fence devices (I did a save/restart after
configuring every major element).

I get exactly the same errors with my more complex cluster.conf file,
containing a more useful configuration :-).
Comment 3 Jim Parsons 2006-10-23 13:06:31 EDT
Fixed in s-c-cluster rhel4 head. Missed an ipmilan attr.
Comment 5 Lon Hohberger 2010-01-22 13:52:27 EST
I verified this fixed in system-config-cluster-1.0.54-2.0; I have not checked prior releases.

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