[ClusterLabs] node went to stand-by after one single resource-failure

[Andrei Borzenkov]

On Mon, Jun 8, 2015 at 3:05 PM, Oscar Salvador
<osalvador.vilardaga at gmail.com> wrote:
> Hi guys!
>
> I've configured two nodes with the stack pacemaker + corosync, with only one
> resource ( just for test purposes ), and I'm having a strange result.
>
> First a little bit of information:
>
> pacemaker version: 1.1.12-1
> corosync version: 2.3.4-1
>
>
> # crm configure show
> node 1053402612: server1 \
> node 1053402613: server2
> primitive IP-rsc_apache IPaddr2 \
> params ip=xx.xx.xx.xy nic=eth0 cidr_netmask=255.255.255.192 \
> meta migration-threshold=2 \
> op monitor interval=20 timeout=60 on-fail=standby
> property cib-bootstrap-options: \
> last-lrm-refresh=1433763004 \
> stonith-enabled=false \
> no-quorum-policy=ignore
>
...
>
>
> It seems like pacemaker is assuming that the monitor-operation failed, and
> because of this, decides to mark the node as a standby. But should not be,
> no?
>

You told it to do exactly that (on-fail=standby).