[Pacemaker] Two slave nodes, neither will promote to Master

[Regendoerp, Achim]

Hi,

I'm currently looking at two VMs which are supposed to mount a drive in
a given directory, depending on who's the master. This was decided above
me, therefore no DRBD stuff (which would've made things easier), but
still using corosync/pacemaker to do the cluster work.

As it is currently, both nodes are online and configured, but none are
switching to Master. In lack of a DRBD resource, I tried using the Dummy
Pacemaker. If that's not the correct RA, please enlighten me on this too.

Below's the current config:

node NODE01 \
        attributes standby="off"
node NODE02 \
        attributes standby="off"
primitive clusterIP ocf:heartbeat:IPaddr2 \
        params ip="10.64.96.31" nic="eth1:1" \
        op monitor on-fail="restart" interval="5s"
primitive clusterIParp ocf:heartbeat:SendArp \
        params ip="10.64.96.31" nic="eth1:1"
primitive fs_nfs ocf:heartbeat:Filesystem \
        params device="/dev/vg_shared/lv_nfs_01" directory="/shared"
fstype="ext4" \
        op start interval="0" timeout="240" \
        op stop interval="0" timeout="240" on-fail="restart"
primitive ms_dummy ocf:pacemaker:Dummy \
        op start interval="0" timeout="240" \
        op stop interval="0" timeout="240" \
        op monitor interval="15" role="Master" timeout="240" \
        op monitor interval="30" role="Slave" on-fail="restart" timeout-240
primitive nfs_share ocf:heartbeat:nfsserver \
        params nfs_ip="10.64.96.31" nfs_init_script="/etc/init.d/nfs"
nfs_shared_infodir="/shared/nfs" nfs_notify_cmd="/sbin/rpc.statd" \
        op start interval="0" timeout="240" \
        op stop interval="0" timeout="240" on-fail="restart"
group Services clusterIP clusterIParp fs_nfs nfs_share \
        meta target-role="Started" is-managed="true"
multiple-active="stop_start"
ms ms_nfs ms_dummy \
        meta target-role="Master" master-max="1" master-node="1"
clone-max="2" clone-node-max="1" notify="true"
colocation services_on_master inf: Services ms_nfs:Master
order fs_before_services inf: ms_nfs:promote Services:start
property $id="cib-bootstrap-options" \
        dc-version="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558" \
        cluster-infrastructure="openais" \
        expected-quorum-votes="2" \
        no-quorum-policy="ignore" \
        stonith-enabled="false"
rsc_defaults $id="rsc-options" \
        resource-stickiness="200"

These are the installed packages

cluster-glue-1.0.5-2.el6.x86_64
cluster-glue-libs-1.0.5-2.el6.x86_64
clusterlib-3.0.12.1-23.el6_2.1.x86_64
corosync-1.4.1-4.el6_2.2.x86_64
corosynclib-1.4.1-4.el6_2.2.x86_64
pacemaker-1.1.6-3.el6.x86_64
pacemaker-cli-1.1.6-3.el6.x86_64
pacemaker-cluster-libs-1.1.6-3.el6.x86_64
pacemaker-libs-1.1.6-3.el6.x86_64
resource-agents-3.9.2-7.el6.x86_64

running on CentOS 6.

If anyone has any idea/suggestion/input/etc. I'd be grateful.

Cheers,

Achim

This email has been sent from Gala Coral Group Limited ("GCG") or a subsidiary or associated company. GCG is registered in England with company number 07254686.   Registered office address: 71 Queensway, London W2 4QH, United Kingdom; website: www.galacoral.com.

This e-mail message (and any attachments) is confidential and may contain privileged and/or proprietorial information protected by legal rules.  It is for use by the intended addressee only. If you believe you are not the intended recipient or that the sender is not authorised to send you the email, please return it to the sender (and please copy it to hq at galacoral.com) and then delete it from your computer.  You should not otherwise copy or disclose its contents to anyone.

Except where this email is sent in the usual course of business, the views expressed are those of the sender and not necessarily ours.  We reserve the right to monitor all emails sent to and from our businesses, to protect the businesses and to ensure compliance with internal policies.

Emails are not secure and cannot be guaranteed to be error-free, as they can be intercepted, amended, lost or destroyed, and may contain viruses; anyone who communicates with us by email is taken to accept these risks.  GCG accepts no liability for any loss or damage which may be caused by software viruses.