Red Hat Bugzilla – Bug 320411
conga should use the node name in cluster.conf and not FQDN for fencing
Last modified: 2009-04-16 18:59:32 EDT
Conga should use the node name found in cluster.conf, not the FQDN (or anything
else that resolves to the same address the name in cluster.conf does) when
calling 'fence_node': if there's any mismatch, 'fence_node' fails immediately.
Note: this doesn't affect normal operation of the cluster. The fence
functionality is provided as a convenience. Users also have the option to reboot
the node, which should work if fence_node doesn't.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
QE ack for RHEL5.2.
verified on a node with two distinct FQDNs.
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.