File 0001-Low-fenced-Correctly-log-the-total-fencing-timeout.patch of Package pacemaker.29834

From c8f12f7e96e7a333dcc7c273b8c99a452368f110 Mon Sep 17 00:00:00 2001
From: Hideo Yamauchi <renayama19661014@ybb.ne.jp>
Date: Tue, 26 Apr 2022 09:18:05 +0900
Subject: [PATCH] Low: fenced: Correctly log the total fencing timeout.

---
 daemons/fenced/fenced_remote.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

Index: pacemaker-2.0.1+20190417.13d370ca9/daemons/fenced/fenced_remote.c
===================================================================
--- pacemaker-2.0.1+20190417.13d370ca9.orig/daemons/fenced/fenced_remote.c
+++ pacemaker-2.0.1+20190417.13d370ca9/daemons/fenced/fenced_remote.c
@@ -1471,14 +1471,12 @@ call_remote_stonith(remote_fencing_op_t
     }
 
     if (!op->op_timer_total) {
-        int total_timeout = get_op_total_timeout(op, peer);
-
-        op->total_timeout = TIMEOUT_MULTIPLY_FACTOR * total_timeout;
+        op->total_timeout = TIMEOUT_MULTIPLY_FACTOR * get_op_total_timeout(op, peer);
         op->op_timer_total = g_timeout_add(1000 * op->total_timeout, remote_op_timeout, op);
         report_timeout_period(op, op->total_timeout);
         crm_info("Total timeout set to %d for peer's fencing of %s for %s"
-                 CRM_XS "id=%s",
-                 total_timeout, op->target, op->client_name, op->id);
+                 CRM_XS "id=%.8s",
+                 op->total_timeout, op->target, op->client_name, op->id);
     }
 
     if (is_set(op->call_options, st_opt_topology) && op->devices) {