[ClusterLabs] "Error: unable to fence '001db02a'" but It got fenced anyway

[Eric Robinson]

> -----Original Message-----
> From: Users <users-bounces at clusterlabs.org> On Behalf Of Valentin Vidic
> Sent: Sunday, February 28, 2021 9:59 AM
> To: users at clusterlabs.org
> Subject: Re: [ClusterLabs] "Error: unable to fence '001db02a'" but It got
> fenced anyway
>
> On Sun, Feb 28, 2021 at 03:34:20PM +0000, Eric Robinson wrote:
> > 001db02b rebooted. After it came back up, I tried it in the other direction.
> >
> > On node 001db02b, the command...
> >
> > # pcs stonith fence 001db02a
> >
> > ...produced output...
> >
> > Error: unable to fence '001db02a'.
> >
> > However, node 001db02a did get restarted!
> >
> > We also saw this error...
> >
> > Failed Actions:
> > * stonith-001db02ab_start_0 on 001db02a 'unknown error' (1): call=70,
> status=Timed Out, exitreason='',
> >     last-rc-change='Sun Feb 28 10:11:10 2021', queued=0ms, exec=20014ms
> >
> > When that happens, does Pacemaker take over the other node's
> resources, or not?
>
> Cloud fencing usually requires a higher timeout (20s reported here).
>
> Microsoft seems to suggest the following setup:
>
> # pcs property set stonith-timeout=900
> # pcs stonith create rsc_st_azure fence_azure_arm username="login ID"
>   password="password" resourceGroup="resource group" tenantId="tenant
> ID"
>   subscriptionId="subscription id"
>   pcmk_host_map="prod-cl1-0:prod-cl1-0-vm-name;prod-cl1-1:prod-cl1-1-
> vm-name"
>   power_timeout=240 pcmk_reboot_timeout=900
> pcmk_monitor_timeout=120
>   pcmk_monitor_retries=4 pcmk_action_limit=3
>   op monitor interval=3600
>

I made the changes and tried again. Fencing took about 3.5 minutes and did not throw an error. Which raises the question, what happens if fencing takes more than 900 seconds? Will Pacemaker on the survivor node refuse to start services if it cannot confirm that the other node has been shot?

-Eric
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.