Red Hat Bugzilla – Bug 207482
system-config-cluster does not reload cluster.conf when incomplete
Last modified: 2009-04-16 18:33:09 EDT
Description of problem:
The system-config-cluster tool may generate a cluster.conf file which is
syntactically correct (from the XML point-overview), but which it cannot reload.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.declare a GFS resource corresponding to a filesystem that still does not exist
2.save the file
3.reload it using system-config-cluster
Relax-NG validity error : Extra element rm in interleave
/root/cluster.conf:2: element cluster: Relax-NG validity error : Element cluster
failed to validate content
/root/cluster.conf fails to validate
no error, but you can click OK to continue, it will succeed.
The problem is caused by the missing "fsid" attribute of a "<fs>" resource.
Since the filesystem did not exist, no fsid has been found.
add an empty attribute in the cluster.conf file:
<fs .... fsid="" .... />
This required alot of consistency fixes between the schema file and the UI,
which I believe are all addressed now - so I am marking this ticket modified as
of build 1.0.36-1.0
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.
Moving all RHCS ver 5 bugs to RHEL 5 so we can remove RHCS v5 which never existed.