[ClusterLabs] Unexpected Resource movement after failover

[Nikhil Utane]

Additional info,

<nvpair id="rsc_defaults-options-resource-stickiness" value="100"
name="resource-stickiness"/>
<nvpair id="rsc_defaults-options-migration-threshold" value="1"
name="migration-threshold"/>

-Nikhil

On Thu, Oct 13, 2016 at 7:29 PM, Nikhil Utane <nikhil.subscribed at gmail.com>
wrote:

> Hi,
>
> I have 5 nodes and 4 resources configured.
> I have configured constraint such that no two resources can be co-located.
> I brought down a node (which happened to be DC). I was expecting the
> resource on the failed node would be migrated to the 5th waiting node (that
> is not running any resource).
> However what happened was the failed node resource was started on another
> active node (after stopping it's existing resource) and that node's
> resource was moved to the waiting node.
>
> What could I be doing wrong?
>
> <nvpair id="cib-bootstrap-options-have-watchdog" value="true"
> name="have-watchdog"/>
> <nvpair id="cib-bootstrap-options-dc-version" value="1.1.14-5a6cdd1"
> name="dc-version"/>
> <nvpair id="cib-bootstrap-options-cluster-infrastructure"
> value="corosync" name="cluster-infrastructure"/>
> <nvpair id="cib-bootstrap-options-stonith-enabled" value="false"
> name="stonith-enabled"/>
> <nvpair id="cib-bootstrap-options-no-quorum-policy" value="ignore"
> name="no-quorum-policy"/>
> <nvpair id="cib-bootstrap-options-default-action-timeout" value="240"
> name="default-action-timeout"/>
> <nvpair id="cib-bootstrap-options-symmetric-cluster" value="false"
> name="symmetric-cluster"/>
>
> # pcs constraint
> Location Constraints:
>   Resource: cu_2
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
>   Resource: cu_3
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
>   Resource: cu_4
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
>   Resource: cu_5
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
> Ordering Constraints:
> Colocation Constraints:
>   cu_3 with cu_2 (score:-INFINITY)
>   cu_4 with cu_2 (score:-INFINITY)
>   cu_4 with cu_3 (score:-INFINITY)
>   cu_5 with cu_2 (score:-INFINITY)
>   cu_5 with cu_3 (score:-INFINITY)
>   cu_5 with cu_4 (score:-INFINITY)
>
> -Thanks
> Nikhil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20161013/9703422d/attachment-0002.html>