On Tue, Nov 29, 2011 at 10:10 AM, Patrick H. pacema...@feystorm.net wrote:
Upgraded to 1.1.6 and put in an ordering constraint, still no joy.
Could you file a bug and include a crm_report for this please?
# crm status
Last updated: Mon Nov 28 23:09:37 2011
Last change: Mon Nov
Sent: Mon Nov 28 2011 16:10:01 GMT-0700 (MST)
From: Patrick H. pacema...@feystorm.net
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org Andreas Kurz andr...@hastexo.com
Subject: Re: [Pacemaker] colocation issue with master-slave resources
Sent: Mon Nov 28 2011 15:27:10
On 11/28/2011 04:51 AM, Patrick H. wrote:
I'm trying to setup a colocation rule so that a couple of master-slave
resources cant be master unless another resource is running on the same
node, and am getting the exact opposite of what I want. The master-slave
resources are getting promoted to
Sent: Mon Nov 28 2011 01:31:22 GMT-0700 (MST)
From: Andreas Kurz andr...@hastexo.com
To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] colocation issue with master-slave resources
On 11/28/2011 04:51 AM, Patrick H. wrote:
I'm trying to setup
Sent: Mon Nov 28 2011 15:27:10 GMT-0700 (MST)
From: Andrew Beekhof and...@beekhof.net
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org Andreas Kurz andr...@hastexo.com
Subject: Re: [Pacemaker] colocation issue with master-slave resources
Perhaps try and ordering
I'm trying to setup a colocation rule so that a couple of master-slave
resources cant be master unless another resource is running on the same
node, and am getting the exact opposite of what I want. The master-slave
resources are getting promoted to master on the node which this other
resource
