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.
DescriptionJaroslav Kortus
2015-03-26 13:49:14 UTC
Description of problem:
# ccs_config_validate -l /etc/cluster/cluster.conf
Unable to update relaxng schema: /tmp/tmp.nZ6gclVfir/cluster.rng:5085: parser error : attributes construct error
uld be unique to a node and have to be written in /etc/multipath.conf. For the "
^
/tmp/tmp.nZ6gclVfir/cluster.rng:5085: parser error : Couldn't find end of Start Tag attribute line 5085
uld be unique to a node and have to be written in /etc/multipath.conf. For the "
^
generated schema does not pass xmllint validation
Under normal circumstances this is hidden from the output so users cannot spot it. But if one makes a mistake in cluster.conf that causes corosync to fail (ipv4 x ipv6 address mix for instance), this error is printed instead and it's quite confusing.
The root cause is probably this snip (taken from fence_agents.rng.cache):
<!-- fence_mpath -->
[ .. redacted .. ]
<optional>
<attribute name="key" rha:description="Key to use for the current operation. This key should be unique to a node and have to be written in /etc/multipath.conf. For the "on" action, the key specifies the key use to register the local node. For the "off" action, this key specifies the key to be removed from the device(s)." />
</optional>
notice the unescaped literals (") that cause xml parsing errors.
Version-Release number of selected component (if applicable):
fence-agents-4.0.15-6.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. ccs_config_validate -l /etc/cluster/cluster.conf
2.
3.
Actual results:
xml errors
Expected results:
clean validation
Additional info:
Description of problem: # ccs_config_validate -l /etc/cluster/cluster.conf Unable to update relaxng schema: /tmp/tmp.nZ6gclVfir/cluster.rng:5085: parser error : attributes construct error uld be unique to a node and have to be written in /etc/multipath.conf. For the " ^ /tmp/tmp.nZ6gclVfir/cluster.rng:5085: parser error : Couldn't find end of Start Tag attribute line 5085 uld be unique to a node and have to be written in /etc/multipath.conf. For the " ^ generated schema does not pass xmllint validation Under normal circumstances this is hidden from the output so users cannot spot it. But if one makes a mistake in cluster.conf that causes corosync to fail (ipv4 x ipv6 address mix for instance), this error is printed instead and it's quite confusing. The root cause is probably this snip (taken from fence_agents.rng.cache): <!-- fence_mpath --> [ .. redacted .. ] <optional> <attribute name="key" rha:description="Key to use for the current operation. This key should be unique to a node and have to be written in /etc/multipath.conf. For the "on" action, the key specifies the key use to register the local node. For the "off" action, this key specifies the key to be removed from the device(s)." /> </optional> notice the unescaped literals (") that cause xml parsing errors. Version-Release number of selected component (if applicable): fence-agents-4.0.15-6.el6.x86_64 How reproducible: always Steps to Reproduce: 1. ccs_config_validate -l /etc/cluster/cluster.conf 2. 3. Actual results: xml errors Expected results: clean validation Additional info: