[Pacemaker] Pacemaker fails to switch on or off PDU sockets with fence_wti

[Andrew Beekhof]

On 20/06/2013, at 1:57 AM, Thibaut Pouzet <thibaut.pouzet at lyra-network.com> wrote:

> Hi,
> 
> I am trying to configure fencing on a test platform with two nodes under corosync+cman+pacemaker on CentOS 6.4. Both nodes have a double power supply from a WTI NPS-8HD16-3. IPMI fencing works like a charm, however I cannot get the WTI fencing to work.
> 
> The problem is that the parameter  action="" seems to be ignored by pacemaker.
> * This is the primitive :
> primitive wti_fence02_port2_off stonith:fence_wti \
>        params ipaddr="" action="off" pcmk_host_check="none" port="A2" pcmk_host_check="static-list" pcmk_host_list="fence02.lyra-network.com" login="" passwd="" shell_timeout="20" login_timeout="20"
> 
> * These are the corresponding log lines :
> Jun 19 16:56:45 fence01 stonith-ng[19266]:   notice: log_operation: Operation 'reboot' [19953] (call 0 from crmd.19268) for host 'fence02.lyra-network.com' with device 'wti_fence02_port2_off' returned: 0 (OK)
> Jun 19 16:56:45 fence01 stonith-ng[19266]:   notice: process_remote_stonith_exec: Call to wti_fence02_port2_off for fence02.lyra-network.com on behalf of crmd.19268 at fence01.lyra-network.com: passed (0)
> 
> * These are the version used :
> pacemaker-1.1.8-7.el6.x86_64
> corosync-1.4.1-15.el6.x86_64
> cman-3.0.12.1-49.el6.x86_64
> fence-agents-3.1.5-25.el6_4.2.x86_64
> 
> The same thing happens with "on" actions.
> 
> When I run fence_wti from command line, it works perfectly fine with ON or OFF actions ! I feel there is a workaround with something like pcmk_reboot_action="/ON", but I don't understand how to use this...
> 
> (FYI, I'm using fencing topology like this :
> fencing_topology \
>        fence01.lyra-network.com: wti_fence01_port1_off,wti_fence01_port5_off,wti_fence01_port5_on,wti_fence01_port1_on ipmi_fence01 \
>        fence02.lyra-network.com: wti_fence02_port2_off,wti_fence02_port6_off,wti_fence02_port6_on,wti_fence02_port2_on ipmi_fence02 )
> 
> What is wrong here ?

I believe you're trying to use the per-agent pcmk_reboot_action option (man stonithd)
But you might be better off with the global stonith-action option (man pengine)