[ClusterLabs] Antw: Re: Antw: [EXT] Re: ocf-tester always claims failure, even with built-in resource agents?

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Mon Mar 29 06:29:25 EDT 2021


>>> Antony Stone <Antony.Stone at ha.open.source.it> schrieb am 29.03.2021 um
10:30 in
Nachricht <202103291030.56200.Antony.Stone at ha.open.source.it>:
> On Monday 29 March 2021 at 09:03:10, Ulrich Windl wrote:
> 
>> >> So, that would be an extra parameter to the resource definition in
>> >> cluster.cib?
>> >> 
>> >> Change:
>> >> 
>> >> primitive Asterisk asterisk meta migration‑threshold=3 op monitor
>> >> interval=5 timeout=30 on‑fail=restart failure‑timeout=10s
>> >> 
>> >> to:
>> >> 
>> >> primitive Asterisk asterisk meta migration‑threshold=3 op monitor
>> >> interval=5 timeout=30 on‑fail=restart failure‑timeout=10s trace_ra=1
>> >> 
>> >>         ?
>> 
>> IMHO it does not make sense to have failure‑timeout smaller than the
>> monitoring interval;
> 
> Um, 10 seconds is not smaller than 5 seconds...

I was referring to "interval=5 timeout=30 failure-timeout=10s"..

Whenever your monitor would time out, the failure would have been reset.

> 
> 
> Antony.
> 
> ‑‑ 
> Your work is both good and original.  Unfortunately the parts that are good

> aren't original, and the parts that are original aren't good.
> 
>  ‑ Samuel Johnson
> 
>                                                    Please reply to the
list;
>                                                          please *don't* CC 
> me.
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/ 





More information about the Users mailing list