Bug 320411 - conga should use the node name in cluster.conf and not FQDN for fencing
conga should use the node name in cluster.conf and not FQDN for fencing
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Ryan McCabe
Depends On:
  Show dependency treegraph
Reported: 2007-10-05 12:25 EDT by Ryan McCabe
Modified: 2009-04-16 18:59 EDT (History)
4 users (show)

See Also:
Fixed In Version: RHBA-2008-0407
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 11:47:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ryan McCabe 2007-10-05 12:25:40 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.
Comment 1 Ryan McCabe 2007-10-05 12:26:46 EDT
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.
Comment 2 RHEL Product and Program Management 2007-10-15 23:35:58 EDT
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
Comment 3 Jay Turner 2007-11-30 01:43:22 EST
QE ack for RHEL5.2.
Comment 5 Brian Brock 2008-05-14 21:49:27 EDT
verified on a node with two distinct FQDNs.  
Comment 7 errata-xmlrpc 2008-05-21 11:47:27 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.