File jsc#ECO-1611-0016-Fix-controller-avoid-possible-use-of-NULL-on-logging.patch of Package pacemaker.16889

From 4fc564b44919a8967d8c6cb0842f5a9699af607b Mon Sep 17 00:00:00 2001
From: "Gao,Yan" <ygao@suse.com>
Date: Tue, 28 Apr 2020 21:01:48 +0200
Subject: [PATCH 16/17] Fix: controller: avoid possible use-of-NULL on logging
 fencing message

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

Index: pacemaker-2.0.1+20190417.13d370ca9/daemons/controld/controld_te_actions.c
===================================================================
--- pacemaker-2.0.1+20190417.13d370ca9.orig/daemons/controld/controld_te_actions.c
+++ pacemaker-2.0.1+20190417.13d370ca9/daemons/controld/controld_te_actions.c
@@ -175,8 +175,10 @@ te_fence_node(crm_graph_t * graph, crm_a
     priority_delay = crm_meta_value(action->params, XML_CONFIG_ATTR_PRIORITY_FENCING_DELAY);
 
     crm_notice("Requesting fencing (%s) of node %s "
-               CRM_XS " action=%s timeout=%u priority_delay=%s",
-               type, target, id, transition_graph->stonith_timeout, priority_delay);
+               CRM_XS " action=%s timeout=%u%s%s",
+               type, target, id, transition_graph->stonith_timeout,
+               priority_delay ? " priority_delay=" : "",
+               priority_delay ? priority_delay : "");
 
     /* Passing NULL means block until we can connect... */
     te_connect_stonith(NULL);