[ClusterLabs] Antw: Re: Antw: [EXT] Failed fencing monitor process (fence_vmware_soap) RHEL 8

[Ulrich Windl]

>>> Ken Gaillot <kgaillot at redhat.com> schrieb am 18.06.2020 um 21:29 in
Nachricht
<9b2cb2273f5e6d54e66e8b432f24c7df73addaa2.camel at redhat.com>:
> On Thu, 2020-06-18 at 21:32 +0300, Andrei Borzenkov wrote:
>> 18.06.2020 18:24, Ken Gaillot пишет:
>> > Note that a failed start of a stonith device will not prevent the
>> > cluster from using that device for fencing. It just prevents the
>> > cluster from monitoring the device.
>> > 
>> 
>> My understanding is that if stonith resource cannot run anywhere, it
>> also won't be used for stonith. When failcount exceeds threshold,
>> resource is banned from node. If it happens on all nodes, resource
>> cannot run anywhere and so won't be used for stonith. Start failure
>> automatically sets failcount to INFINITY.
>> 
>> Or do I misunderstand something?
> 
> I had to test to confirm, but a stonith resource stopped due to
> failures can indeed be used. Only stonith resources stopped via
> location constraints (bans) or target-role=Stopped are prevented from
> being used.

Yes, that's what I knew: Stonith can be used on a node where the stonith
"resource" isn't running. Before I had wondered why the stonith resource isn't
cloned for each node...

> -- 
> Ken Gaillot <kgaillot at redhat.com>
> 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/