File bsc#1198715-0001-Log-controller-log-an-info-instead-of-a-warning-for-.patch of Package pacemaker.27558

From 8276b144b28ab3f77bcb9aec98a5d3a809e7b705 Mon Sep 17 00:00:00 2001
From: "Gao,Yan" <ygao@suse.com>
Date: Thu, 7 Jul 2022 10:50:40 +0200
Subject: [PATCH] Log: controller: log an info instead of a warning for a
 stonith/shutdown that is unknown to the new DC

If it happens to be the old DC that has just shut down, the new DC may
bring up this warning anyway. Although the message is more from the new
DC's point of view purely regarding whether the event matches any
running cluster transition, but it's confusing to end users since the
shutdown was scheduled and should be "expected".

Fixes T454
---
 daemons/controld/controld_callbacks.c | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

Index: pacemaker-2.0.4+20200616.2deceaa3a/daemons/controld/controld_callbacks.c
===================================================================
--- pacemaker-2.0.4+20200616.2deceaa3a.orig/daemons/controld/controld_callbacks.c
+++ pacemaker-2.0.4+20200616.2deceaa3a/daemons/controld/controld_callbacks.c
@@ -286,8 +286,13 @@ peer_update_callback(enum crm_status_typ
             }
 
         } else if (appeared == FALSE) {
-            crm_warn("Stonith/shutdown of node %s was not expected",
-                     node->uname);
+            if (transition_graph == NULL || transition_graph->id == -1) {
+                crm_info("Stonith/shutdown of node %s is unknown to the "
+                         "current DC", node->uname);
+            } else {
+                crm_warn("Stonith/shutdown of node %s was not expected",
+                         node->uname);
+            }
             if (!is_remote) {
                 crm_update_peer_join(__FUNCTION__, node, crm_join_none);
                 check_join_state(fsa_state, __FUNCTION__);