Red Hat Bugzilla – Bug 453371
fence_bladecenter cannot set_power_state
Last modified: 2009-04-16 16:35:20 EDT
Description of problem:
Fenced daemon fails to fence IBM blade center node.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Turn off one of machines which is in failover configuration.
2. Wait for messages "fence "node" failed.
Node not fenced, cluster disabled.
Node fenced, cluster ok.
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
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
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.
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.