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.
DescriptionBrandon Perkins
2011-03-16 16:54:33 UTC
Description of problem:
fence_rhevm fence_agent group definition missing from the cluster.conf Relax-NG schema.
Version-Release number of selected component (if applicable):
cman/cluster-3.0.12-23.el6_0.4
How reproducible:
Always.
Steps to Reproduce:
1. Add a fence_rhevm fencedevice element to a RHEL6 cluster.conf. Example:
<fencedevices>
<fencedevice agent="fence_rhevm" ipaddr="##.##.###.###" login="USERNAME" name="HOSTNAME" passwd="PASSWORD" power_wait="30" shell_timeout="12" ssl="1"/>
</fencedevices>
2. Run 'ccs_config_validate'
Actual results:
[root@rhel60node-01 ~]# ccs_config_validate
Relax-NG validity error : Extra element fencedevices in interleave
tempfile:119: element fencedevices: Relax-NG validity error : Element cluster failed to validate content
Configuration fails to validate
Expected results:
[root@rhel60node-01 ~]# ccs_config_validate
Configuration validates
Additional info:
The identical bock works fine on RHEL5 with system-config-cluster-1.0.57-7
Patch forthcoming.
Description of problem: fence_rhevm fence_agent group definition missing from the cluster.conf Relax-NG schema. Version-Release number of selected component (if applicable): cman/cluster-3.0.12-23.el6_0.4 How reproducible: Always. Steps to Reproduce: 1. Add a fence_rhevm fencedevice element to a RHEL6 cluster.conf. Example: <fencedevices> <fencedevice agent="fence_rhevm" ipaddr="##.##.###.###" login="USERNAME" name="HOSTNAME" passwd="PASSWORD" power_wait="30" shell_timeout="12" ssl="1"/> </fencedevices> 2. Run 'ccs_config_validate' Actual results: [root@rhel60node-01 ~]# ccs_config_validate Relax-NG validity error : Extra element fencedevices in interleave tempfile:119: element fencedevices: Relax-NG validity error : Element cluster failed to validate content Configuration fails to validate Expected results: [root@rhel60node-01 ~]# ccs_config_validate Configuration validates Additional info: The identical bock works fine on RHEL5 with system-config-cluster-1.0.57-7 Patch forthcoming.