On Wed, Jan 19, 2011 at 10:20 AM, Florian Haas wrote:
> On 01/18/2011 10:15 PM, Evgeniy Ivanov wrote:
Is it expected (PM 1.0.3)? What's correct way to achieve this?
>>>
>>> Consider upgrading.
>>
>> Yeah, I will. But for now I need to make it work on 1.0.3.
>
> IIRC there were a _bunch_ of is
On 01/18/2011 10:15 PM, Evgeniy Ivanov wrote:
>>> Is it expected (PM 1.0.3)? What's correct way to achieve this?
>>
>> Consider upgrading.
>
> Yeah, I will. But for now I need to make it work on 1.0.3.
IIRC there were a _bunch_ of issues of exactly the type you mentioned
that were fixed in the 1.
On Tue, Jan 18, 2011 at 6:37 PM, Dejan Muhamedagic wrote:
> Hi,
>
> On Tue, Jan 18, 2011 at 02:52:07PM +0300, Evgeniy Ivanov wrote:
>> Hello,
>>
>> I have a group Gr and multistate resource MasterRsc. I need MasterRsc
>> to be master on the node where Gr works.
>> In MasterRsc::start() I use crm_m
Hi,
On Tue, Jan 18, 2011 at 02:52:07PM +0300, Evgeniy Ivanov wrote:
> Hello,
>
> I have a group Gr and multistate resource MasterRsc. I need MasterRsc
> to be master on the node where Gr works.
> In MasterRsc::start() I use crm_master to set higher value if Gr works
> on this node and it works fi
Hello,
I have a group Gr and multistate resource MasterRsc. I need MasterRsc
to be master on the node where Gr works.
In MasterRsc::start() I use crm_master to set higher value if Gr works
on this node and it works fine.
But I have a problem with failovers and colocation:
I did failover of Gr a
