[Pacemaker] Force Pacemaker to not monitor resources on a node

[Felix Zachlod]

Hello List,

I am currently trying to add a third node only for giving a quorum a to 
the cluster in case a servicing node fails. But oviously I can't get it 
right.

The third node is forced to standby and I put a location constraint just 
like described in:

http://clusterlabs.org/wiki/DRBD_HowTo_1.0#Specifying_the_nodes_where_the_DRBD_RA_can_be_run

this is from my config:

node $id="beafcd74-f991-4e77-ae82-a8ad0a76f8a1" storage-test-d
node $id="d001b7e3-5c97-4913-8fe7-764fcf67416f" storage-voter \
         attributes standby="on"
node $id="deb75c11-7d06-4b6d-ae7b-f64eead63a54" storage-test-c
primitive drbd_testdata1 ocf:linbit:drbd \
         params drbd_resource="testdata1" \
         op monitor interval="29s" role="Master" \
         op monitor interval="31s" role="Slave"
primitive st-storage-test-c stonith:null \
         params hostlist="storage-test-c"
primitive st-storage-test-d stonith:null \
         params hostlist="storage-test-d"
ms ms_drbd_testdata1 drbd_testdata1 \
         meta master-max="1" master-node-max="1" clone-max="2" 
clone-node-max="1" notify="true"
location l-st-node1 st-storage-test-c -inf: storage-test-c
location l-st-node2 st-storage-test-d -inf: storage-test-d
location l_ms_drbd_testdata1 ms_drbd_testdata1 \
         rule $id="l_ms_drbd_testdata1-rule" -inf: #uname ne 
storage-test-c and #uname ne storage-test-d
property $id="cib-bootstrap-options" \
         dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \
         cluster-infrastructure="Heartbeat" \
         expected-quorum-votes="2" \
         last-lrm-refresh="1411727659"

So there are three nodes storage-test-c, storage-test-d and 
storage-voter. The resource is being started correctly on storage-test-c 
and storage-test-d but pacemaker keeps monitoring the resource on 
storage-voter complaining it is "not installed" which is correct as this 
node will never hold any resource actually. It just has the same network 
connections as the other ones and should be helping to decide if a node 
is actually down or just isolated.

This is the message from crm status:

Failed actions:
     drbd_testdata1:0_monitor_0 (node=storage-voter, call=9, rc=5, 
status=complete): not installed

Can anyone give me a hint how to solve this? As said storage-voter will 
never run any resource although it would be nive if it could trigger 
stonith actions anyway.

Thank you all in advance,
best regards, Felix