Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJan Pokorný [poki]
2010-09-20 19:51:05 UTC
Description of problem:
It was found that current fence_egenera man page on updated RHEL 6 is missing "user" ("-u") parameter.
In addition, cluster.rng does not support "lpan", "pserver", mentioned "user" and looking forward, maybe also "delay" parameters in connection with this fence agent. This makes validation of cluster.conf involving this fence agent failing. "cserver" parameter is okay in this concern.
Version-Release number of selected component (if applicable):
$ rpm -q fence-agents
fence-agents-3.0.12-8.el6.x86_64
(also upstream repository was explored and no fix found)
Steps to Reproduce (for failing validation of cluster.conf against cluster.rng and using hypothetical one-node cluster for simplicity):
1.
$ cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster config_version="90" name="testcluster-new">
<fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
<clusternodes>
<clusternode name="node1" nodeid="1" votes="1">
<fence>
<method name="test_method">
<device lpan="test_lpan" name="test_egenera" pserver="test_pserver"/>
</method>
</fence>
</clusternode>
</clusternodes>
<cman/>
<fencedevices>
<fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera"/>
</fencedevices>
<rm>
<failoverdomains/>
<resources/>
</rm>
</cluster>
2.
$ xmllint --relaxng /usr/share/cluster/cluster.rng --noout /etc/cluster/cluster.conf.invalid
Relax-NG validity error : Extra element fence in interleave
/etc/cluster/cluster.conf.invalid:4: element clusternodes: Relax-NG validity error : Element clusternode failed to validate content
/etc/cluster/cluster.conf.invalid:5: element clusternode: Relax-NG validity error : Element clusternodes has extra content: clusternode
/etc/cluster/cluster.conf.invalid fails to validate
Actual results:
Unsuccessful validation.
Expected results:
Successful validation.
Additional info:
If mentioned parameters are removed from the example above, it looks like this:
$ cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster config_version="90" name="testcluster-new">
<fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
<clusternodes>
<clusternode name="node1" nodeid="1" votes="1">
<fence>
<method name="test_method">
<device name="test_egenera"/>
</method>
</fence>
</clusternode>
</clusternodes>
<cman/>
<fencedevices>
<fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera"/>
</fencedevices>
<rm>
<failoverdomains/>
<resources/>
</rm>
</cluster>
$ xmllint --relaxng /usr/share/cluster/cluster.rng --noout /etc/cluster/cluster.conf
/etc/cluster/cluster.conf validates
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0745.html
Description of problem: It was found that current fence_egenera man page on updated RHEL 6 is missing "user" ("-u") parameter. In addition, cluster.rng does not support "lpan", "pserver", mentioned "user" and looking forward, maybe also "delay" parameters in connection with this fence agent. This makes validation of cluster.conf involving this fence agent failing. "cserver" parameter is okay in this concern. Version-Release number of selected component (if applicable): $ rpm -q fence-agents fence-agents-3.0.12-8.el6.x86_64 (also upstream repository was explored and no fix found) Steps to Reproduce (for failing validation of cluster.conf against cluster.rng and using hypothetical one-node cluster for simplicity): 1. $ cat /etc/cluster/cluster.conf <?xml version="1.0"?> <cluster config_version="90" name="testcluster-new"> <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/> <clusternodes> <clusternode name="node1" nodeid="1" votes="1"> <fence> <method name="test_method"> <device lpan="test_lpan" name="test_egenera" pserver="test_pserver"/> </method> </fence> </clusternode> </clusternodes> <cman/> <fencedevices> <fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera"/> </fencedevices> <rm> <failoverdomains/> <resources/> </rm> </cluster> 2. $ xmllint --relaxng /usr/share/cluster/cluster.rng --noout /etc/cluster/cluster.conf.invalid Relax-NG validity error : Extra element fence in interleave /etc/cluster/cluster.conf.invalid:4: element clusternodes: Relax-NG validity error : Element clusternode failed to validate content /etc/cluster/cluster.conf.invalid:5: element clusternode: Relax-NG validity error : Element clusternodes has extra content: clusternode /etc/cluster/cluster.conf.invalid fails to validate Actual results: Unsuccessful validation. Expected results: Successful validation. Additional info: If mentioned parameters are removed from the example above, it looks like this: $ cat /etc/cluster/cluster.conf <?xml version="1.0"?> <cluster config_version="90" name="testcluster-new"> <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/> <clusternodes> <clusternode name="node1" nodeid="1" votes="1"> <fence> <method name="test_method"> <device name="test_egenera"/> </method> </fence> </clusternode> </clusternodes> <cman/> <fencedevices> <fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera"/> </fencedevices> <rm> <failoverdomains/> <resources/> </rm> </cluster> $ xmllint --relaxng /usr/share/cluster/cluster.rng --noout /etc/cluster/cluster.conf /etc/cluster/cluster.conf validates