On 14.04.2023 14:35, Andrei Borzenkov wrote:
On Fri, Apr 14, 2023 at 11:45 AM Philip Schiller
wrote:
I would like to know if the order constraint
is equivalent to: "First promote ms-drbd_fs then start drbd_vm".
No, it is not. It is equivalent to
order drbd_vm_after_drbd_fs Mandatory:
On Fri, Apr 14, 2023 at 2:35 PM Andrei Borzenkov wrote:
>
> As far as I can tell, pacemaker simply does not support migration
> together with demote/promote actions. I don't really know the reasons.
Thinking about it - migrating a resource depending on a master is
simply not possible in the
On Fri, Apr 14, 2023 at 11:45 AM Philip Schiller
wrote:
>
> I would like to know if the order constraint Mandatory: ms-drbd_fs:promote drbd_vm>
> is equivalent to: "First promote ms-drbd_fs then start drbd_vm".
>
No, it is not. It is equivalent to
order drbd_vm_after_drbd_fs Mandatory:
Hello Andrei,
I'm sorry for the confusion. I will try to point everything out more specific.
*>>Andrei Borzenkov*
/>>Thu Apr 13 15:24:38 EDT 2023 /In this Message you tested the behavior of my thread.
OK, I compared CIB and the difference is that non-working case has
explicit "start" action
On Fri, Apr 14, 2023 at 10:25 AM Philip Schiller
wrote:
>
> Thank you very much Andrei,
> this completely solved my problem.
>
I am not sure I understand that (and as you do not quote the previous
posts you are replying to it is not even clear what you are talking
about).
> To point out, when
Thank you very much Andrei,
this completely solved my problem.
To point out, when I use the command:
pcs constraint order promote mas-drbd-jabber pri-vm-jabber
it sets the pri-vm action to start as default -> order
order-mas-drbd-jabber-pri-vm-jabber-mandatory mas-drbd-jabber:promote