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: