[Pacemaker] problem with location and role

Marcus marcus at undecided-aim.de
Thu Nov 10 11:07:42 EST 2011

Hi there,

I have a problem with pacemaker 1.0.9 on heartbeat on a 2 node cluster. 
I created some resources and a dummy resource to move around.

here is the config:

node $id="07c9653f-22c3-47be-8b52-cd8da183ce2e" debian60-clnode1
node $id="f97d4817-7043-4644-bcf0-57159233acea" debian60-clnode2
primitive priNICcheck ocf:heartbeat:ethmonitor \
         params interface="eth0" name="ifEth0" multiplier="200" \
         operations $id="priNICcheck-operations" \
         op monitor interval="10" timeout="60" start-delay="0"
primitive priTest ocf:heartbeat:Dummy
clone clnNICcheck priNICcheck
location locNICok priTest \
         rule $id="locNICok-rule" $role="started" 500: #uname eq 
debian60-clnode2 \
         rule $id="locNICok-rule2" ifEth0: defined ifEth0
property $id="cib-bootstrap-options" \
         stonith-enabled="false" \
         dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
         no-quorum-policy="ignore" \
         cluster-infrastructure="Heartbeat" \
rsc_defaults $id="rsc-options" \

As I understand rule locNICok-rule2 should set the score of priTest to 
500 if it is running on debian60-clnode2. Is that correct? Because it 
doesn't do so. When I turn of eth0 at node1 it swaps to node2 and gets a 
score of 300 (ifEth0 + sticky).
Background - I want the resource to stay on node2 even if eth0 on node1 
comes back and eth0 on node2 fails.

Thanks in advance.

More information about the Pacemaker mailing list