Bug 229662 - XML validation errors when using DRAC fencing with Blades
XML validation errors when using DRAC fencing with Blades
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
4
All Linux
low Severity low
: ---
: ---
Assigned To: Ryan McCabe
Cluster QE
:
Depends On:
Blocks: 247731
  Show dependency treegraph
 
Reported: 2007-02-22 11:30 EST by Andrew Cathrow
Modified: 2014-09-07 18:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-01-22 14:23:18 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)
Sample cluster.conf created by s-config-cluster (731 bytes, application/octet-stream)
2007-02-22 11:30 EST, Andrew Cathrow
no flags Details
Patch to allow modulename as a parameter in xml for drac interfaces. (342 bytes, patch)
2007-07-11 00:02 EDT, Wade Mealing
no flags Details | Diff

  None (edit)
Description Andrew Cathrow 2007-02-22 11:30:13 EST
Description of problem:


Version-Release number of selected component (if applicable):
Running RHEL4U4 x86 with all errata applied.
System-config-cluster is version 1.0.27-1.0

After setting up cluster.conf to use DRAC fencing with a Dell Blade system the
system-config-cluster tool gives an XML validation error.



tmp/cluster.conf:8: element device: Relax-NG validity error : Invalid attribute
modulename for element device
Relax-NG validity error : Extra element fence in interleave
/tmp/cluster.conf:4: element clusternodes: Relax-NG validity error : Element
clusternode failed to validate content
/tmp/cluster.conf:5: element clusternode: Relax-NG validity error : Element
clusternodes has extra content: clusternode
/tmp/cluster.conf:6: element fence: Relax-NG validity error : Element
clusternode has extra content: fence
/tmp/cluster.conf:2: element cluster: Relax-NG validity error : Invalid sequence
in interleave
/tmp/cluster.conf:2: element cluster: Relax-NG validity error : Element cluster
failed to validate content
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf fails to validate



How reproducible:
100%tmp/cluster.conf:8: element device: Relax-NG validity error : Invalid
attribute modulename for element device
Relax-NG validity error : Extra element fence in interleave
/tmp/cluster.conf:4: element clusternodes: Relax-NG validity error : Element
clusternode failed to validate content
/tmp/cluster.conf:5: element clusternode: Relax-NG validity error : Element
clusternodes has extra content: clusternode
/tmp/cluster.conf:6: element fence: Relax-NG validity error : Element
clusternode has extra content: fence
/tmp/cluster.conf:2: element cluster: Relax-NG validity error : Invalid sequence
in interleave
/tmp/cluster.conf:2: element cluster: Relax-NG validity error : Element cluster
failed to validate content
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf:8: element device: validity error : IDREF attribute name
references an unknown ID "drac-frame"
/tmp/cluster.conf fails to validate



Steps to Reproduce:
This error occurs if you use the modulename option with DRAC fencing to specify
the module within a blade chassis.
See attached sample cluster.conf- created in system-config-cluster


The fix seems to be adding a modulename section to the FENCE schema.
Tested ok with my customer's configuration file.

 <group> 
  <attribute name="modulename"/>
 </group>
Comment 1 Andrew Cathrow 2007-02-22 11:30:13 EST
Created attachment 148589 [details]
Sample cluster.conf created by s-config-cluster
Comment 2 Wade Mealing 2007-07-11 00:02:05 EDT
Created attachment 158922 [details]
Patch to allow modulename as a parameter in xml for drac interfaces.

Apparently fixed as mentioned in:
http://post-office.corp.redhat.com/archives/cluster-list/2007-February/msg00215.html


But this does not work. This may also be valid for RHEL5 clusters also.
Comment 3 Wade Mealing 2007-07-11 20:11:13 EDT
Ok, looks like its fixed over in the other bzilla by parsons.
Comment 5 Lon Hohberger 2010-01-22 14:23:18 EST
This is fixed in system-config-cluster-1.0.54-2.0.  I did not check earlier releases.  Not sure why it wasn't closed.

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