[Pacemaker] Moving cloned resources

[Andrew Beekhof]

On 09/08/2013, at 4:25 AM, "Matias R. Cuenca del Rey" <maticue at gmail.com> wrote:

> Hi,
> 
> This is my first mail. I'm playing with active/active cluster with cman+pacemaker
> I have 3 nodes working great. When I reboot one node, my IP resource move to another node, but when the rebooted node comes back, my IP resource doesn't move in again.

Why would it?  You haven't used a location constraint to tell the cluster to prefer that node.

> I tried to move mannualy with pcs but I get the following error:

You can't move instances of a clone.

> 
> [root at www-proxylb01 ~]# pcs config
> Corosync Nodes:
>  
> Pacemaker Nodes:
>  www-proxylb01 www-proxylb02 www-proxylb03 
> 
> Resources: 
>  Clone: ip-xxx.xxx.xxx.xxx-clone
>   Resource: ip-xxx.xxx.xxx.xxx (provider=heartbeat type=IPaddr2 class=ocf)
>    Attributes: ip=xxx.xxx.xxx.xxx cidr_netmask=32 clusterip_hash=sourceip-sourceport 
>    Operations: monitor interval=30s
>  Clone: fs-usr.share.haproxy-clone
>   Resource: fs-usr.share.haproxy (provider=heartbeat type=Filesystem class=ocf)
>    Attributes: device=/dev/xvdc directory=/usr/share/haproxy/ fstype=gfs2 
>  Clone: haproxy-xxx.xxx.xxx.xxx-clone
>   Resource: haproxy-xxx.xxx.xxx.xxx (provider=heartbeat type=haproxy class=ocf)
>    Attributes: conffile=/etc/haproxy/haproxy.cfg 
>    Operations: monitor interval=30s
> 
> Location Constraints:
> Ordering Constraints:
>   ip-xxx.xxx.xxx.xxx-clone then haproxy-xxx.xxx.xxx.xxx-clone
>   fs-usr.share.haproxy-clone then haproxy-xxx.xxx.xxx.xxx-clone
> Colocation Constraints:
>   haproxy-xxx.xxx.xxx.xxx-clone with ip-xxx.xxx.xxx.xxx-clone
>   haproxy-xxx.xxx.xxx.xxx-clone with fs-usr.share.haproxy-clone
>   fs-usr.share.haproxy-clone with ip-xxx.xxx.xxx.xxx-clone
> 
> Cluster Properties:
>  dc-version: 1.1.8-7.el6-394e906
>  cluster-infrastructure: cman
>  expected-quorum-votes: 2
>  stonith-enabled: false
>  resource-stickiness: 100
> 
> 
> [root at www-proxylb01 ~]# pcs status
> Last updated: Thu Aug  8 15:17:09 2013
> Last change: Wed Aug  7 16:32:10 2013 via crm_attribute on www-proxylb01
> Stack: cman
> Current DC: www-proxylb03 - partition with quorum
> Version: 1.1.8-7.el6-394e906
> 3 Nodes configured, 2 expected votes
> 9 Resources configured.
> 
> 
> Online: [ www-proxylb01 www-proxylb02 www-proxylb03 ]
> 
> Full list of resources:
> 
>  Clone Set: ip-xxx.xxx.xxx.xxx-clone [ip-xxx.xxx.xxx.xxx] (unique)
>      ip-xxx.xxx.xxx.xxx:0    (ocf::heartbeat:IPaddr2):    Started www-proxylb01
>      ip-xxx.xxx.xxx.xxx:1    (ocf::heartbeat:IPaddr2):    Started www-proxylb01
>      ip-xxx.xxx.xxx.xxx:2    (ocf::heartbeat:IPaddr2):    Started www-proxylb03
>  Clone Set: fs-usr.share.haproxy-clone [fs-usr.share.haproxy]
>      Started: [ www-proxylb01 www-proxylb03 ]
>      Stopped: [ fs-usr.share.haproxy:2 ]
>  Clone Set: haproxy-xxx.xxx.xxx.xxx-clone [haproxy-xxx.xxx.xxx.xxx]
>      Started: [ www-proxylb01 www-proxylb03 ]
>      Stopped: [ haproxy-xxx.xxx.xxx.xxx:2 ]
> 
> [root at www-proxylb01 ~]# pcs resource move ip-xxx.xxx.xxx.xxx:1 www-proxylb02
> Error moving/unmoving resource
> Error performing operation: Update does not conform to the configured schema
> 
> Thanks a lot in advance
> 
> 
> Matías R. Cuenca del Rey
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org