[Pacemaker] crm resource move doesn't move the resource

Pavlos Parissis pavlos.parissis at gmail.com
Sat Oct 2 12:31:12 EDT 2010


Hi,

I am having again the same issue, in a different set of 3 nodes. When I try
to failover manually the resource group on the standby node, the ms-drbd
resource is not moved as well and as a result the resource group is not
fully started, only the ip resource is started.
Any ideas why I am having this issue?

here are the info
[root at node-01 ~]# crm resource move pbx_service_01 node-03
[root at node-01 ~]# crm resource unmove pbx_service_01
[root at node-01 ~]# ptest -Ls
Allocation scores:
clone_color: ms-drbd_01 allocation score on node-01: 100
clone_color: ms-drbd_01 allocation score on node-03: 0
clone_color: drbd_01:0 allocation score on node-01: 11100
clone_color: drbd_01:0 allocation score on node-03: 0
clone_color: drbd_01:1 allocation score on node-01: 100
clone_color: drbd_01:1 allocation score on node-03: 11000
native_color: drbd_01:0 allocation score on node-01: 11100
native_color: drbd_01:0 allocation score on node-03: 0
native_color: drbd_01:1 allocation score on node-01: -1000000
native_color: drbd_01:1 allocation score on node-03: 11000
drbd_01:0 promotion score on node-01: 10100
drbd_01:1 promotion score on node-03: 10000
drbd_01:2 promotion score on none: 0
group_color: pbx_service_01 allocation score on node-01: 200
group_color: pbx_service_01 allocation score on node-03: 10
group_color: ip_01 allocation score on node-01: 200
group_color: ip_01 allocation score on node-03: 1010
group_color: fs_01 allocation score on node-01: 0
group_color: fs_01 allocation score on node-03: 0
group_color: pbx_01 allocation score on node-01: 0
group_color: pbx_01 allocation score on node-03: 0
native_color: ip_01 allocation score on node-01: 200
native_color: ip_01 allocation score on node-03: 1010
drbd_01:0 promotion score on node-01: 1000000
drbd_01:1 promotion score on node-03: -1000000
drbd_01:2 promotion score on none: 0
native_color: fs_01 allocation score on node-01: -1000000
native_color: fs_01 allocation score on node-03: -1000000
native_color: pbx_01 allocation score on node-01: -1000000
native_color: pbx_01 allocation score on node-03: -1000000


[root at node-01 ~]# crm status
============
Last updated: Sat Oct  2 18:27:32 2010
Stack: Heartbeat
Current DC: node-03 (3dd75a8f-9819-450f-9f18-c27730665925) - partition with
quorum
Version: 1.0.9-89bd754939df5150de7cd76835f98fe90851b677
3 Nodes configured, unknown expected votes
2 Resources configured.
============

Online: [ node-03 node-01 node-02 ]

 Master/Slave Set: ms-drbd_01
     Masters: [ node-01 ]
     Slaves: [ node-03 ]
 Resource Group: pbx_service_01
     ip_01      (ocf::heartbeat:IPaddr2):       Started node-03
     fs_01      (ocf::heartbeat:Filesystem):    Stopped
     pbx_01     (lsb:test-01):  Stopped


[root at node-01 ~]# crm configure show
node $id="3dd75a8f-9819-450f-9f18-c27730665925" node-03
node $id="4e47db29-5f14-4371-9734-317bf342b8ed" node-02
node $id="a8f56e42-438f-4ea5-a6ba-a7f1d23ed401" node-01
primitive drbd_01 ocf:linbit:drbd \
        params drbd_resource="drbd_pbx_service_1" \
        op monitor interval="30s" \
        op start interval="0" timeout="240s" \
        op stop interval="0" timeout="120s"
primitive fs_01 ocf:heartbeat:Filesystem \
        params device="/dev/drbd1" directory="/pbx_service_01" fstype="ext3"
\
        meta migration-threshold="3" failure-timeout="60" \
        op monitor interval="20s" timeout="40s" OCF_CHECK_LEVEL="20" \
        op start interval="0" timeout="60s" \
        op stop interval="0" timeout="60s"
primitive ip_01 ocf:heartbeat:IPaddr2 \
        params ip="192.168.78.10" cidr_netmask="24"
broadcast="192.168.78.255" \
        meta failure-timeout="120" migration-threshold="3" \
        op monitor interval="5s"
primitive pbx_01 lsb:test-01 \
        meta migration-threshold="3" failure-timeout="60" \
        op monitor interval="20s" timeout="20s" \
        op start interval="0" timeout="60s" \
        op stop interval="0" timeout="60s"
group pbx_service_01 ip_01 fs_01 pbx_01 \
        meta target-role="Started"
ms ms-drbd_01 drbd_01 \
        meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Started"
location PrimaryNode-drbd_01 ms-drbd_01 100: node-01
location PrimaryNode-pbx_service_01 pbx_service_01 200: node-01
location SecondaryNode-drbd_01 ms-drbd_01 0: node-03
location SecondaryNode-pbx_service_01 pbx_service_01 10: node-03
colocation fs_01-on-drbd_01 inf: fs_01 ms-drbd_01:Master
order pbx_service_01-after-drbd_01 inf: ms-drbd_01:promote
pbx_service_01:start
property $id="cib-bootstrap-options" \
        dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \
        cluster-infrastructure="Heartbeat" \
        symmetric-cluster="false" \
        stonith-enabled="false"
rsc_defaults $id="rsc-options" \
        resource-stickiness="1000"
[root at node-01 ~]#

Thanks,
Pavlos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101002/a59bde2e/attachment-0001.html>


More information about the Pacemaker mailing list