Bug 439444

Summary: fence_apc does not fence cluster node
Product: Red Hat Enterprise Linux 5 Reporter: Thomas Walker <walker>
Component: cmanAssignee: Jim Parsons <jparsons>
Status: CLOSED NOTABUG QA Contact: GFS Bugs <gfs-bugs>
Severity: urgent Docs Contact:
Priority: low    
Version: 5.1CC: cluster-maint, edamato, rmccabe
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-31 12:15:49 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 Thomas Walker 2008-03-28 18:17:58 UTC 
Description of problem:

RHEL 5.1 Cluster, kernel 2.6.18-53.1.13.el5
cman version cman-2.0.73-1.el5_1.1
APC Master switch APC7901, firmware apc_hw02_aos357_rpdu356.exe

Related to Bugzilla 245675,396581 but fix listed in those still does not work.

fencing of a node produces nothing.  Tried fencing a node from luci and with
fence_node -O but neither works.  No errors, process just sits there;

root      6756  5321  0 14:06 pts/0    00:00:00 fence_node -O 10.0.0.3
root      6757  6756  1 14:06 pts/0    00:00:00 /usr/bin/python /sbin/fence_apc

However, an interactive fence_apc command does work, so the switch is answering;

# fence_apc -a 10.0.0.24 -l apc -p apc -n 1 -o Status
Status check successful. Port 1 is ON


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

see above


How reproducible:

  Very.  Sending a fence command from luci or with fence_node does not produce
any result or error.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Thomas Walker 2008-03-31 11:53:48 UTC 
   Apparently I was in error somehow.  I rebuilt the cluster config from scratch
and now fencing works.  You can close this case.

 Thomas Walker