[ClusterLabs] ocf:pacemaker:ping works strange

Artem tyomikh at gmail.com
Tue Dec 12 10:08:29 EST 2023

Hi Andrei. pingd==0 won't satisfy both statements. It would if I used GTE,
but I used GT.
pingd lt 1 --> [0]
pingd gt 0 --> [1,2,3,...]

On Tue, 12 Dec 2023 at 17:21, Andrei Borzenkov <arvidjaar at gmail.com> wrote:

> On Tue, Dec 12, 2023 at 4:47 PM Artem <tyomikh at gmail.com> wrote:
> >> > pcs constraint location FAKE3 rule score=0 pingd lt 1 or not_defined
> pingd
> >> > pcs constraint location FAKE3 rule score=125 pingd gt 0 or defined
> pingd
> > Are they really contradicting?
> Yes. pingd == 0 will satisfy both rules. My use of "always" was
> incorrect, it does not happen for all possible values of pingd, but it
> does happen for some.

May be defined/not_defined should be put in front of lt/gt ? It is possible
that VM goes down, pingd to not_defined, then the rule evaluates "lt 1"
first, catches an error and doesn't evaluate next part (after OR)?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20231212/6c1b1b8b/attachment.htm>

More information about the Users mailing list