File 0001-Clear-out-the-DIR_EXECUTABLE-variable-so-we-catch-th.patch of Package resource-agents.22880

From ce27a1573a9e407a514229fb03356a0d9c08a2db Mon Sep 17 00:00:00 2001
From: Ondrej Famera <ondrej@famera.cz>
Date: Mon, 30 Apr 2018 21:09:44 +0200
Subject: [PATCH 1/1] Clear out the $DIR_EXECUTABLE variable so we catch the
 situation when we lose the directory with binaries after first
 sapinstance_init invokation. The second sapinstance_init invocation will not
 detect it as it will have already preset the $DIR_EXECUTABLE from previous
 run. This may allow us running actions after second sapinstance_init
 invocation that would be not run if we knew that we miss the needed binaries.

This affect the following functions/operations:
- sapinstance_monitor_clone
- sapinstance_promote_clone
- sapinstance_demote_clone

This is limited to only Master/Slave resource and only when the
sapinstance_init is invoked multiple times during one operation.
---
 heartbeat/SAPInstance | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/heartbeat/SAPInstance b/heartbeat/SAPInstance
index bff1a260..47e1d095 100755
--- a/heartbeat/SAPInstance	2021-08-30 07:43:59.376226391 +0200
+++ b/heartbeat/SAPInstance	2021-08-30 08:13:55.731073704 +0200
@@ -367,6 +367,8 @@
   InstanceNr=`echo "$InstanceName" | sed 's/.*\([0-9][0-9]\)$/\1/'`
   SAPVIRHOST=`echo "$myInstanceName" | cut -d_ -f3`
 
+  # make sure that we don't care the content of variable from previous run of sapinstance_init
+  DIR_EXECUTABLE=""
   # optional OCF parameters, we try to guess which directories are correct
   if  [ -z "$OCF_RESKEY_DIR_EXECUTABLE" ]
   then