File bsc#1171372-0002-Fix-libstonithd-action-parameter-of-RHCS-style-fence.patch of Package pacemaker.26413

From c0b7b77571ca5b6b10b08d08f9c8b71c4455427a Mon Sep 17 00:00:00 2001
From: "Gao,Yan" <ygao@suse.com>
Date: Wed, 15 Apr 2020 19:39:29 +0200
Subject: [PATCH 2/2] Fix: libstonithd: `action` parameter of RHCS-style
 fence-agents is shown as non-required in the metadata

The parameter `action` of RHCS-style fence-agents shouldn't usually be
specified in fencing resource configuration, although it'd be properly
remapped anyways with 9c0c3d60b4.

With this commit, the parameter `action` of RHCS-style fence-agents is
fudged to be shown as `required="0"` in the metadata output by
`stonith_admin --metadata` or `crm_resource --show-metadata`. So that
users know they don't have to configure it. Pacemaker handles and passes
the parameter to the agent when executing it.
---
 lib/fencing/st_client.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Index: pacemaker-1.1.18+20180430.b12c320f5/lib/fencing/st_client.c
===================================================================
--- pacemaker-1.1.18+20180430.b12c320f5.orig/lib/fencing/st_client.c
+++ pacemaker-1.1.18+20180430.b12c320f5/lib/fencing/st_client.c
@@ -1219,7 +1219,8 @@ stonith_api_device_metadata(stonith_t *
 
         freeXpathObject(xpathObj);
 
-        /* Now fudge the metadata so that the port isn't required in the configuration */
+        // Fudge metadata so parameters are not required in config (pacemaker adds them)
+        stonith_rhcs_parameter_not_required(xml, "action");
         stonith_rhcs_parameter_not_required(xml, "port");
         free(buffer);
         buffer = dump_xml_formatted_with_text(xml);