[ClusterLabs] Antw: [EXT] Re: Q: How to clean up a failed fencing operation?

[Ulrich Windl]

>>> Reid Wahl <nwahl at redhat.com> schrieb am 03.05.2022 um 10:16 in Nachricht
<CAPiuu98BFCiG8gkUOGLXYEyFjdOTahFeTXjWP79dBxDO71RTtA at mail.gmail.com>:
> On Tue, May 3, 2022 at 12:36 AM Ulrich Windl
> <Ulrich.Windl at rz.uni‑regensburg.de> wrote:
>>
>> Hi!
>>
>> I'm familiar with cleaning up various failed resource actions via 
> "crm_resource ‑C ‑r resource_name ‑N node_name ‑n operation".
>> However I wonder wha tthe correct paraneters for a failed fencing operation

> (that lingers around) are.
> 
> stonith_admin ‑‑history '*' ‑‑cleanup

Ah, a completely different command! Interestingly this does not produce any
logs in syslog (no DC action).

Regards,
Ulrich


> 
>>
>> crm_mon found:
>> Failed Fencing Actions:
>>   * reboot of h18 failed: delegate=h16,
client=stonith_admin.controld.22336, 
> origin=h18, last‑failed='2022‑04‑27 02:22:52 +02:00' (a later attempt
succeeded)
>>
>> Regards,
>> Ulrich
>>
>>
>>
>> _______________________________________________
>> Manage your subscription:
>> https://lists.clusterlabs.org/mailman/listinfo/users 
>>
>> ClusterLabs home: https://www.clusterlabs.org/ 
>>
> 
> 
> ‑‑ 
> Regards,
> 
> Reid Wahl (He/Him), RHCA
> Senior Software Maintenance Engineer, Red Hat
> CEE ‑ Platform Support Delivery ‑ ClusterHA
> 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/