Bug 187283 - `service fenced status` returns 1 when fenced is running (should return 0)
Summary: `service fenced status` returns 1 when fenced is running (should return 0)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: fence
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Marek Grac
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-29 19:17 UTC by Stanko Kupcevic
Modified: 2009-12-22 21:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-22 21:20:50 UTC
Embargoed:

Attachments (Terms of Use)

Description Stanko Kupcevic 2006-03-29 19:17:25 UTC 
Description of problem:
`/etc/init.d/fenced status` returns 1 when fenced is running (should return 0).

This causes problems for conga, when it determines cluster status and
starts/stops a node. 

'status' deviates from behavior of other init scripts, and so is a bug. 


Version-Release number of selected component (if applicable):
fence-1.32.18-0

How reproducible:
Always
Comment 1 Jim Parsons 2006-08-08 13:13:29 UTC 
This is fixed in 4.4
Comment 2 Lon Hohberger 2009-12-22 21:20:50 UTC 
Verified in fence-1.32.67-1.el4, but was probably fixed earlier.
Note You need to log in before you can comment on or make changes to this bug.