File bsc#1210074-0006-Fix-fencer-apply-requested-fencing-delay-only-for-th.patch of Package pacemaker.38495

From dd563f99570865582810cfa17374f141849a95b8 Mon Sep 17 00:00:00 2001
From: "Gao,Yan" <ygao@suse.com>
Date: Thu, 13 Apr 2023 14:29:56 +0200
Subject: [PATCH 06/11] Fix: fencer: apply requested fencing delay only for the
 first device

... per review. No need to delay for further devices.
---
 daemons/fenced/fenced_remote.c | 8 ++++++++
 1 file changed, 8 insertions(+)

Index: pacemaker-2.0.5+20201202.ba59be712/daemons/fenced/fenced_remote.c
===================================================================
--- pacemaker-2.0.5+20201202.ba59be712.orig/daemons/fenced/fenced_remote.c
+++ pacemaker-2.0.5+20201202.ba59be712/daemons/fenced/fenced_remote.c
@@ -591,7 +591,16 @@ remote_op_timeout_one(gpointer userdata)
     op->op_timer_one = 0;
 
     crm_notice("Peer's '%s' action targeting %s for client %s timed out " CRM_XS
-               " id=%s", op->action, op->target, op->client_name, op->id);
+               " id=%.8s", op->action, op->target, op->client_name, op->id);
+
+    // The requested delay has been applied for the first device
+    if (op->delay > 0) {
+        op->delay = 0;
+        crm_trace("Try another device for '%s' action targeting %s "
+                  "for client %s without delay " CRM_XS " id=%.8s",
+                  op->action, op->target, op->client_name, op->id);
+    }
+
     call_remote_stonith(op, NULL, pcmk_ok);
     return FALSE;
 }