Bug 453371

Summary:	fence_bladecenter cannot set_power_state
Product:	[Retired] Red Hat Cluster Suite	Reporter:	janusz <janusz.syrytczyk>
Component:	fence	Assignee:	Jim Parsons <jparsons>
Status:	CLOSED NOTABUG	QA Contact:	Cluster QE <mspqa-list>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	4	CC:	cluster-maint, edamato
Target Milestone:	---
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-07-01 09:51:08 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 janusz 2008-06-30 07:56:16 UTC

Description of problem:

Fenced daemon fails to fence IBM blade center node.

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

fence_bladecenter 1.32.50

How reproducible:

50%.

Steps to Reproduce:
1. Turn off one of machines which is in failover configuration.
2. Wait for messages  "fence "node" failed.
  
Actual results:

Node not fenced, cluster disabled.

Expected results:

Node fenced, cluster ok.

Description:

I want to fence blade in IBM BladeCenter. All goes ok when I want to fence node
1. It goes down, cluster is degraded but serves fine.

But when I want to fence node 3 (blade is in slot 3 and 4). I issue:

fence_bladecenter -a 172.16.3.100 -l properusername -n 3 properpassword -o off 

and get:

unexpected powerstate

If I turn off the 3th blade I got in logs: 
fencing node "nodename"
agent "fence_bladecenter" reports: unexpected powerstate

I have to mention that when I issue:

fence_bladecenter -a 172.16.3.100 -l properusername -n 3 properpassword -o status

I get:

success: blade3 status: On

I can easily operate on node 1, but not 3. I guess 2 issues are possible:
fence_bladecenter's function get_power_state / set_power_state is wrong or the
BladeCenter is malfunctioning.

Thanks,
Janusz.

Comment 1 janusz 2008-07-01 09:51:08 UTC

OK, this is NOT a bug.

fence_bladecenters' function (set_power_state) has no function to recognize
permission errors. In my case the issue was in BladeCenter, which apparently
needed to delete/recreate the authenticating user.