[Pacemaker] Invoking "crm node standby" command on active command leads to stopping of resource on both Active and standby node

[neha chatrath]

Hello,
I am using a cluster with following configuration:

 [root at MCG1 neha]# crm configure show
node $id="0686a4d1-c9de-4334-8d33-1a9f6f0755dd" ggns2mexsatsdp22
node $id="76246d46-f0e4-4ba8-9179-d60aa7c697c8" ggns2mexsatsdp23
node $id="9d59c9e6-24e0-4684-94ab-c07af7e7a2f0" mcg1 \
        attributes standby="off"
node $id="fb3f06f0-05bf-42ef-a312-c072f589918a" mcg2 \
        attributes standby="off"
primitive ClusterIP ocf:mcg:MCG_VIPaddr_RA \
        params ip="192.168.113.77" cidr_netmask="255.255.255.0"
nic="eth0:1" \
        op monitor interval="40" timeout="20"
primitive RM ocf:mcg:RM_RA \
        op monitor interval="60" role="Master" timeout="30"
on-fail="restart" \
        op monitor interval="40" role="Slave" timeout="40" on-fail="restart"
primitive Tmgr ocf:mcg:TM_RA \
        op monitor interval="60" role="Master" timeout="30"
on-fail="restart" \
        op monitor interval="40" role="Slave" timeout="40" on-fail="restart"
primitive pimd ocf:mcg:PIMD_RA \
        op monitor interval="60" role="Master" timeout="30"
on-fail="standby" \
        op monitor interval="40" role="Slave" timeout="40" on-fail="restart"
ms ms_RM RM \
        meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Started"
ms ms_Tmgr Tmgr \
        meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Started"
ms ms_pimd pimd \
        meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Started"
colocation ip_with_RM inf: ClusterIP ms_RM:Master
colocation ip_with_Tmgr inf: ClusterIP ms_Tmgr:Master
colocation ip_with_pimd inf: ClusterIP ms_pimd:Master
order TM-after-RM inf: ms_RM:promote ms_Tmgr:start
order ip-after-pimd inf: ms_pimd:promote ClusterIP:start
order pimd-after-TM inf: ms_Tmgr:promote ms_pimd:start
property $id="cib-bootstrap-options" \
        dc-version="1.0.11-55a5f5be61c367cbd676c2f0ec4f1c62b38223d7" \
        cluster-infrastructure="Heartbeat" \
        no-quorum-policy="ignore" \
        stonith-enabled="false"
rsc_defaults $id="rsc-options" \
        resource-stickiness="100" \
        migration-threshold="3"

When I execute "crm node standby" command on the Active node, it leads to
stopping of resourcs on both Active and Standby node.
As per my understanding, this should lead to stopping of resources only on
current Active node and all the resources on the standby node should get a
promote.

Please comment.

Thanks and regards
Neha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120110/420cf6bb/attachment-0003.html>