[Linux-HA] Need explanation for colocation constraint

[Yan Fitterer]

Actually, just seen that the SP1 hasn't _quite_ made it out the door
yet. Any time soon, though! Sorry for the confusion.

Yan Fitterer wrote:
> I _think_ that 2.0.7 had a bug on that that was fixed later (2.0.8?).
> Novell has just released SP1, with a vastly improved Heartbeat package.
> Try reproducing the issue with the upgraded version.
> 
> matilda matilda wrote:
>> Hi all,
>>
>> after reading almost all stuff on linux-ha.org, digging around in the mailing list
>> and doing many tries on a test cluster installation (HAv2, version 2.0.7 as of SuSE SLES 10)
>> I do have a phenomena I can't explain to myself.
>>
>> Probably someone can help.
>>
>> What I want:
>> * 3 IP-resources (works well)
>> * for every IP a places-contraint (works)
>> * ldirectord resource (works almost)
>>
>> Now: I want that ldirectord starts on the
>> same node as one of the ip resources.
>> If ldirectord has to start it should start on
>> the same node as ip1 or ip2 or ip3.
>>
>> I created a colocation constraint for every ip.
>>
>> And now: As soon as I stop the resource ldirectord
>> all my ip resources are also shut down.
>> Why this? I don't habe a before/after-orders-constraint.
>>
>> Best regards
>> Andreas Mock
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA at lists.linux-ha.org
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems