fence_ipmilan fails or times out after updating fence-agents even though the timeout option is specified in the configuration in a RHEL 6 High Availability cluster
Issue
- I have a 2 node Red Hat High availability cluster. After upgrading to RHEL 6.7, the
timeoutoption no longer is valid for the fencing agents defined in the stanzasfencedevicessection of/etc/cluster/cluster.conf. - When `ccs_config_validate is ran it fails with the following output:
# ccs_config_validate -f /etc/cluster/cluster.conf
Relax-NG validity error : Extra element fencedevices in interleave
tempfile:8: element fencedevices: Relax-NG validity error : Element cluster failed to validate content
Configuration fails to validate
- After patching the operating system, the
cluster.confno longer validates. Manually copying the samecluster.confto another server with older RHEL6.6 release, it validates fine.
[root@node1 cluster ]# ccs_config_validate
Relax-NG validity error : Extra element fencedevices in interleave
tempfile:49: element fencedevices: Relax-NG validity error : Element cluster failed to validate content
tempfile:36: element device: validity error : IDREF attribute name references an unknown ID "IPMI-02"
tempfile:29: element device: validity error : IDREF attribute name references an unknown ID "IPMI-01"
Configuration fails to validate
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
fence-agents-4.0.15-8.el6.x86_64or later- One or more
fencedevices configured in/etc/cluster/cluster.confusing one of the following agents:fence_ilo3fence_ilo4fence_immfence_idracfence_ipmilan
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
