Blame SOURCES/bz1848673-sybaseASE-verify-start-action-only.patch

e72037
From 953f689cb2a37606b6d4b2250ebec23f129f5095 Mon Sep 17 00:00:00 2001
e72037
From: Reid wahl <nrwahl@protonmail.com>
e72037
Date: Thu, 9 Jul 2020 23:32:22 -0700
e72037
Subject: [PATCH] sybaseASE: Run verify_all() for start operation only
e72037
e72037
The `sybaseASE` resource agent runs the `verify_all()` function at the
e72037
beginning of start, stop, and monitor operations.
e72037
e72037
When `verify_all()` is run for a probe (monitor) operation and
e72037
`sybase_home` resides on a cluster-managed filesystem, the probe often
e72037
fails with `$OCF_ERR_GENERIC` because the filesystem isn't mounted yet.
e72037
This prevents the resource from starting on that node.
e72037
e72037
For the stop operation, there's simply no reason to run `verify_all()`.
e72037
e72037
This patch removes `verify_all()` for the stop and monitor operations.
e72037
It is now only run for the start operation.
e72037
e72037
Resolves: RHBZ#1848673
e72037
Resolves: RHBZ#1848025
e72037
---
e72037
 heartbeat/sybaseASE.in | 2 --
e72037
 1 file changed, 2 deletions(-)
e72037
e72037
diff --git a/heartbeat/sybaseASE.in b/heartbeat/sybaseASE.in
e72037
index 9ddd429be..7ff30bd31 100755
e72037
--- a/heartbeat/sybaseASE.in
e72037
+++ b/heartbeat/sybaseASE.in
e72037
@@ -864,12 +864,10 @@ case $__OCF_ACTION in
e72037
 		exit $?
e72037
 		;;
e72037
 	stop)
e72037
-		verify_all || exit $OCF_ERR_GENERIC
e72037
 		ase_stop
e72037
 		exit $?
e72037
 		;;
e72037
 	status | monitor)
e72037
-		verify_all || exit $OCF_ERR_GENERIC
e72037
 		ase_status $OCF_CHECK_LEVEL
e72037
 		exit $?
e72037
 		;;