Hi Ken,
I've tried with and without colocation. The rule was:
colocation bla2 inf: VM_VM1 AA_Filesystem_CDrive1
In both cases the VM_VM1 tries to live migrate back the coming after standby
node while cloned AA_Filesystem_CDrive1 isn't up on it yet.
Same result with pacemaker 1.14-rc2
Regards,
On 12/16/2015 10:30 AM, Klechomir wrote:
> On 16.12.2015 17:52, Ken Gaillot wrote:
>> On 12/16/2015 02:09 AM, Klechomir wrote:
>>> Hi list,
>>> I have a cluster with VM resources on a cloned active-active storage.
>>>
>>> VirtualDomain resource migrates properly during failover (node standby),
>>>
On 16.12.2015 17:52, Ken Gaillot wrote:
On 12/16/2015 02:09 AM, Klechomir wrote:
Hi list,
I have a cluster with VM resources on a cloned active-active storage.
VirtualDomain resource migrates properly during failover (node standby),
but tries to migrate back too early, during failback, ignoring
On 12/16/2015 02:09 AM, Klechomir wrote:
> Hi list,
> I have a cluster with VM resources on a cloned active-active storage.
>
> VirtualDomain resource migrates properly during failover (node standby),
> but tries to migrate back too early, during failback, ignoring the
> "order" constraint, tellin
Hi list,
I have a cluster with VM resources on a cloned active-active storage.
VirtualDomain resource migrates properly during failover (node standby),
but tries to migrate back too early, during failback, ignoring the
"order" constraint, telling it to start when the cloned storage is up.
This
