[Pacemaker] Resource not starting automatically after node standby

[Andrew Beekhof]

cluster version, config and logs would be a good starting point.
probably best to use crm_report to create a support tarball.

On 14 May 2014, at 12:42 am, W Forum W <wforumw at gmail.com> wrote:

> Hi 
> 
> I have a cluster with 2 nodes, with DRBD
> I have configured a few resources in one group
> If I migrate the group everything will be stopped correctly and started on the other node
> I can also migrate it back without problems.
> Now if I put the Master node in standby or reboot the group is not migrated to the other node. But the Slave node becomes Master
> DRBD is migrate fine but no resources are migrated.
> If the server comes back online, the resources are started again
> 
> How can I configure the cluster that the resource are migrated if the Master node is down or in standby? Or the Resources should always start on the Master
> 
> Many thanks
> _______________________________________________
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140514/b3165ff7/attachment-0004.sig>