With fence-1.32.6-0: fence_node will not pass an action to the underlying fencing program. From the strace: 8128 read(0, "agent=fence_ipmilan\nipaddr=172.16.115.22\nlogin=regit\npasswd=gogo\n", 16384) = 65 Test: # cat test agent=fence_ipmilan ipaddr=172.16.115.22 login=regit passwd=gogo # cat test | fence_ipmilan failed: operation must be 'on', 'off', or 'reboot' All the other fencing methods (although RPS10 is also affected) use "reboot" as the default. Patch attached. (Another way to do it would be for fence_node to always pass an action, but some fencing methods don't support it either).
Created attachment 117401 [details] fence-set-default-action.patch
Arguably, this is not a bug. While most of the other agents do have a default action, that doesn't mean that all agents HAVE to have a default action. Removing the default option forces the ccs information to be more specific, which is a very good thing. The reason that 'reboot' is a dangerous default action is because it does not work for nodes that require more than one fencing device. Take for example nodes that have two powersupplies. They will require two fencing devices to be configured for that node. If the default action of all the agents is reboot, this can allow the user mistakenly think that they are rebooting both power supplies at the same time, when infact, it is done serially resulting in a node that is never actually powered off. Moving forward, it is actually safer to have the default action be off/disable or have no default action at all. The down side of which is that it will require modifications for all current users.
*** This bug has been marked as a duplicate of 164627 ***