Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 159685 - fenced init script should not faiil if it's a gulm cluster
fenced init script should not faiil if it's a gulm cluster
Product: Red Hat Cluster Suite
Classification: Retired
Component: fence (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adam "mantis" Manthei
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2005-06-06 18:45 EDT by Corey Marthaler
Modified: 2009-04-16 15:56 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2005-737
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-07 12:55:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:737 normal SHIPPED_LIVE fence bug fix update 2005-10-07 00:00:00 EDT

  None (edit)
Description Corey Marthaler 2005-06-06 18:45:52 EDT
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 16:55:32 EDT
Fix applied to the following versions in CVS for cluster/fence/init.d/fenced:
   HEAD:   1.5 
Comment 2 Corey Marthaler 2005-08-30 18:16:23 EDT
fix verified.
Comment 3 Red Hat Bugzilla 2005-10-07 12:55:25 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 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.


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