[ClusterLabs] Antw: [EXT] Cluster Removing VIP and Not Following Order Constraint

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Fri Feb 11 02:11:20 EST 2022

>>> Jonno <jstk888 at gmail.com> schrieb am 10.02.2022 um 20:43 in Nachricht
<CADGLmTe311U71NKSEBoeogkk+WcCHpt44MH1T-4hy-=J-NL8Tw at mail.gmail.com>:
> 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
> move rsc_cluster_vip node2".
> When running the command above, I am asking the cluster to migrate the VIP
> to the standby node, but I am expecting the cluster to honour the order
> constraint, by first running the script resource named "rsc_lsb_quiesce".
> The order constraint looks like:
> "order order_ABC rsc_lsb_quiesce rsc_cluster_vip msl_ABC:promote
> rsc_lsb_resume"
> But it doesn't seem to do what I expect. It always removes the VIP entirely
> from the cluster first, then it starts to follow the order constraint. This
> means my cluster is in a state where the VIP is completely gone for a
> couple of minutes. I've also tried doing a "crm resource move 
> rsc_lsb_quiesce
> node2" hoping to trigger the script resource first, but the cluster always
> removes the VIP before doing anything.
> My question is: How can I make the cluster follow this order constraint? I

I'm very sure you just made a configuration mistake.
But nobody can help you unless you show your configuration and example execution of events, plus the expected order of execution.


> need the cluster to run the "rsc_lsb_quiesce" script against a remote
> application server before any other action is taken. I especially need the
> VIP to stay where it is. Should I be doing this another way?
> Regards,
> Jonathan

More information about the Users mailing list