Ah, it's a HANA.
Last HANA I did had something like this:
colocation constraint-> VIP with Master HANAorder constraint -> First HANA
clone (don't specify master role) -> then IP
That way ,when the standby HANA joins and the master is demoted (kind of
challanged) and afterwards samo old primary
Hello all,
Thank you for your assistance.
Below is the config from my lab environment. By the way, I just tried
Strahil's suggestions, but it didn't seem to have any effect on the
behaviour.
Regards,
Jonathan
node 1: senzhana3 \
attributes hana_abc_op_mode=logreplay
On Fri, Feb 11, 2022 at 9:13 AM Strahil Nikolov via Users <
users@clusterlabs.org> wrote:
> Shouldn't you use kind ' Mandatory' and simetrical TRUE ?
>
> If true, the reverse of the constraint applies for the opposite action
> (for example, if B starts after A starts, then B stops before A
Shouldn't you use kind ' Mandatory' and simetrical TRUE ?
If true, the reverse of the constraint applies for the opposite action (for
example, if B starts after A starts, then B stops before A stops).
Best Regards,Strahil Nikolov
On Fri, Feb 11, 2022 at 9:11, Ulrich Windl
wrote: >>>
>>> Jonno schrieb am 10.02.2022 um 20:43 in Nachricht
:
> Hello,
>
> I am having some trouble getting my 2 node active/passive cluster to do
> what I want. More specifically, my cluster is removing the VIP from the
> cluster whenever I attempt a failover with a command such as "crm resource
>
