Bug 159685

Summary:	fenced init script should not faiil if it's a gulm cluster
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Corey Marthaler <cmarthal>
Component:	fence	Assignee:	Adam "mantis" Manthei <amanthei>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	cluster-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2005-737	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-07 16:55:25 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 Corey Marthaler 2005-06-06 22:45:52 UTC

Description of problem:
Similiar to bz 153741, with a Gulm cluster, there is no reason to run the
'fence_tool join' cmd and then have a failure in the syslog:
"Starting fence domain:[FAILED]"

It should skip it just like the 'cman_tool join' and then output a warning.

Comment 1 Adam "mantis" Manthei 2005-07-27 20:55:32 UTC

Fix applied to the following versions in CVS for cluster/fence/init.d/fenced:
   HEAD:   1.5 
   RHEL4:  1.1.2.4 
   STABLE: 1.1.2.2.4.1.2.1

Comment 2 Corey Marthaler 2005-08-30 22:16:23 UTC

fix verified.

Comment 3 Red Hat Bugzilla 2005-10-07 16:55:25 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 the 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-2005-737.html