Bug 320411

Summary:	conga should use the node name in cluster.conf and not FQDN for fencing
Product:	Red Hat Enterprise Linux 5	Reporter:	Ryan McCabe <rmccabe>
Component:	conga	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.1	CC:	cluster-maint, jparsons, pkennedy, rkenna
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2008-0407	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-21 15:47:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ryan McCabe 2007-10-05 16:25:40 UTC

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 16:26:46 UTC

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 Program Management 2007-10-16 03:35:58 UTC

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
release.

Comment 3 Jay Turner 2007-11-30 06:43:22 UTC

QE ack for RHEL5.2.

Comment 5 Brian Brock 2008-05-15 01:49:27 UTC

verified on a node with two distinct FQDNs.

Comment 7 errata-xmlrpc 2008-05-21 15:47:27 UTC

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.

http://rhn.redhat.com/errata/RHBA-2008-0407.html