[Pacemaker] clone ip definition and location stops my resources...

[Gianluca Cecchi]

Hello,
using pacemaker 1.0.8 on rh el 5 I have some problems understanding the way
ping clone works to setup monitoring of gw... even after reading docs...

As soon as I run:
crm configure location nfs-group-with-pinggw nfs-group rule -inf:
not_defined pinggw or pinggw lte 0

the resources go stopped and don't re-start....

Then, as soon as I run
crm configure delete nfs-group-with-pinggw

the resources of the group start again...

config (part of it, actually) I try to apply is this:
group nfs-group ClusterIP lv_drbd0 NfsFS nfssrv \
meta target-role="Started"
ms NfsData nfsdrbd \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1"
notify="true"
primitive pinggw ocf:pacemaker:ping \
params host_list="192.168.101.1" multiplier="100" \
op start interval="0" timeout="90" \
op stop interval="0" timeout="100"
clone cl-pinggw pinggw \
meta globally-unique="false"
location nfs-group-with-pinggw nfs-group \
rule $id="nfs-group-with-pinggw-rule" -inf: not_defined pinggw or pinggw lte
0

Is the location constraint to be done with ping resource or with its clone?
Is it a cause of the problem that I have also defined an nfs client on the
other node with:

primitive nfsclient ocf:heartbeat:Filesystem \
params device="nfsha:/nfsdata/web" directory="/nfsdata/web" fstype="nfs" \
op start interval="0" timeout="60" \
op stop interval="0" timeout="60"
colocation nfsclient_not_on_nfs-group -inf: nfs-group nfsclient
order nfsclient_after_nfs-group inf: nfs-group nfsclient

Thansk in advance,
Gianluca