fix HANA_CALL inner timeouts prevent proper logging

SAPHanaSR.changes_12

@@ -1,3 +1,56 @@
+-------------------------------------------------------------------
+Wed Jan 29 14:24:15 UTC 2024 - [email protected]
+
+- Version bump to 0.162.3
+  * Fix the hexdump log for empty node states
+  * catch monitor calls for non-cloned resources and report them as
+    unsupported instead of 'command not found'
+    (bsc#1218333)
+  * fix scope of variable 'site' to be global
+    (bsc#1219194)
+  * susChkSrv.py - relocate function logTimestamp()
+  * update man pages:
+    SAPHanaSR.7
+    ocf_suse_SAPHana.7
+    SAPHanaSR_maintenance_examples.7
+    SAPHanaSR.py.7
+    SAPHanaSR-showAttr.8
+
+-------------------------------------------------------------------
+Thu Nov  2 17:50:47 UTC 2023 - [email protected]
+
+- Version bump to 0.162.2
+  * inside SAPHanaSR-hookHelper use the full path for the cibadmin
+    command to support non root users in special user environments
+    (bsc#1216484)
+  * if the SAPHanaSR.py hook has successfully reported a SR event
+    to the cluster a still existing fall-back state file will be
+    removed to prevent an override of an already reported
+    SR state.
+    (bsc#1215693)
+  * improve supportability by providing the current process ID of
+    the RA, which is logged in the RA outputs, to HANA tracefiles
+    too.
+    This allows a mapping of the SAP related command invocations
+    from the RA and the HANA executions which might have a delay
+    in between.
+    (bsc#1214613)
+  * avoid explicid and implicid usage of /tmp filesystem to keep
+    the SAPHanaSR resource agents working even in situations with
+    /tmp filesystem full.
+    (bsc#1210728)
+  * update man pages:
+    SAPHanaSR.7
+    SAPHanaSR_basic_cluster.7
+    SAPHanaSR_maintenance_examples.7
+    ocf_suse_SAPHana.7
+    ocf_suse_SAPHanaTopology.7
+    susCostOpt.py.7
+    SAPHanaSR-monitor.8
+    SAPHanaSR-showAttr.8
+  * add improvements from SAP to the RA scripts, part II
+    (jsc#PED-1739, jsc#PED-2608)
+
 -------------------------------------------------------------------
 Tue Jan 24 15:27:27 UTC 2023 - [email protected]
 

SAPHanaSR.changes_15

@@ -1,3 +1,56 @@
+-------------------------------------------------------------------
+Wed Jan 29 14:31:20 UTC 2024 - [email protected]
+
+- Version bump to 0.162.3
+  * Fix the hexdump log for empty node states
+  * catch monitor calls for non-cloned resources and report them as
+    unsupported instead of 'command not found'
+    (bsc#1218333)
+  * fix scope of variable 'site' to be global
+    (bsc#1219194)
+  * susChkSrv.py - relocate function logTimestamp()
+  * update man pages:
+    SAPHanaSR.7
+    ocf_suse_SAPHana.7
+    SAPHanaSR_maintenance_examples.7
+    SAPHanaSR.py.7
+    SAPHanaSR-showAttr.8
+
+-------------------------------------------------------------------
+Thu Nov  2 17:49:47 UTC 2023 - [email protected]
+
+- Version bump to 0.162.2
+  * inside SAPHanaSR-hookHelper use the full path for the cibadmin
+    command to support non root users in special user environments
+    (bsc#1216484)
+  * if the SAPHanaSR.py hook has successfully reported a SR event
+    to the cluster a still existing fall-back state file will be
+    removed to prevent an override of an already reported
+    SR state.
+    (bsc#1215693)
+  * improve supportability by providing the current process ID of
+    the RA, which is logged in the RA outputs, to HANA tracefiles
+    too.
+    This allows a mapping of the SAP related command invocations
+    from the RA and the HANA executions which might have a delay
+    in between.
+    (bsc#1214613)
+  * avoid explicid and implicid usage of /tmp filesystem to keep
+    the SAPHanaSR resource agents working even in situations with
+    /tmp filesystem full.
+    (bsc#1210728)
+  * update man pages:
+    SAPHanaSR.7
+    SAPHanaSR_basic_cluster.7
+    SAPHanaSR_maintenance_examples.7
+    ocf_suse_SAPHana.7
+    ocf_suse_SAPHanaTopology.7
+    susCostOpt.py.7
+    SAPHanaSR-monitor.8
+    SAPHanaSR-showAttr.8
+  * add improvements from SAP to the RA scripts, part II
+    (jsc#PED-1739, jsc#PED-2608)
+
 -------------------------------------------------------------------
 Tue Jan 24 15:27:27 UTC 2023 - [email protected]
 

SAPHanaSR.spec

@@ -3,7 +3,7 @@
 #
 # Copyright (c) 2013-2014 SUSE Linux Products GmbH, Nuernberg, Germany.
 # Copyright (c) 2014-2016 SUSE Linux GmbH, Nuernberg, Germany.
-# Copyright (c) 2017-2023 SUSE LLC.
+# Copyright (c) 2017-2024 SUSE LLC.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -23,7 +23,7 @@ License:        GPL-2.0
 Group:          Productivity/Clustering/HA
 AutoReqProv:    on
 Summary:        Resource agents to control the HANA database in system replication setup
-Version:        0.162.1
+Version:        0.162.3
 Release:        0
 Url:            http://scn.sap.com/community/hana-in-memory/blog/2014/04/04/fail-safe-operation-of-sap-hana-suse-extends-its-high-availability-solution
 

man/SAPHanaSR-monitor.8

@@ -33,7 +33,7 @@ The overall system replication (SR) state is shown in an summarized manner.
 .HP
 \fB --intervall \fISEC\fR
 .br
-	repeat with intervall of \fISEC\fR seconds, default is 10 seconds.
+	repeat with interval of \fISEC\fR seconds, default is 10 seconds.
 .HP
 \fB --nodes \fINUM\fR
 .br

man/SAPHanaSR-showAttr.8

@@ -1,6 +1,6 @@
-.\" Version: 0.160.1
+.\" Version: 0.162.1
 .\"
-.TH SAPHanaSR-showAttr 8 "11 Nov 2022" "" "SAPHanaSR"
+.TH SAPHanaSR-showAttr 8 "24 Jan 2024" "" "SAPHanaSR"
 .\"
 .SH NAME
 SAPHanaSR-showAttr \- Shows Linux cluster attributes for SAP HANA system replication.
@@ -43,6 +43,8 @@ HANA replication channel state, indicated by srConnectionChanged (\fBsrHook\fP)
 .br
 HANA replication state of secondary site, indicated by systemReplicationStatus.py (\fBsync_state\fP)
 .br
+HANA replication mode (\fBsrmode\fP)
+.br
 Linux cluster update status (\fBupd\fP)
 .TP
 Resource section
@@ -52,6 +54,7 @@ name of Linux cluster resource (\fBResource\fP)
 maintenance status of Linux cluster resource (\fBmaintenance\fP)
 .TP
 Site section
+.br
 HANA site name (\fBSite\fP)
 .br
 SAPHanaSR last primary timestamp (\fBlpt\fP)
@@ -140,7 +143,7 @@ ocf_suse_SAPHanaController(7).
 Value: [ \fIgeneration\fR ]
 
 The RA generation attribute identifies which generation of the RA is running.
-It helps determing RA's capabilities and performing cluster-wide upgrades of
+It helps determining RA's capabilities and performing cluster-wide upgrades of
 RA and srHook. The generation should be same for both on all nodes of the
 Linux cluster after successful upgrade.
 See also gsh below and SAPHanaSR-manageAttr(8).
@@ -151,7 +154,7 @@ See also gsh below and SAPHanaSR-manageAttr(8).
 Value: [ \fIgeneration\fR ]
 
 The srHook generation attribute identifies which generation of the srHook is running.
-It helps determing srHook's capabilities and performing cluster-wide upgrades of
+It helps determining srHook's capabilities and performing cluster-wide upgrades of
 RA and srHook. E.g. starting with generation 2.0 the RA supports scale-out
 multi-target system replication, which needs replacement of the old SAPHanaSR.py
 by new SAPHanaSrMultiTarget.py.
@@ -266,7 +269,7 @@ Value: [ online | offline ]
 
 Value: [ logreplay | delta_datashipping | logreplay_readaccess ]
 
-The node attribute hana_<sid>_op_mode is set by SAPHanaTopology, according to the running HANA. The attribute is used by the SAPHanaController or SAPHana resource agent for setting up system replication. delta_datashipping is not recommended in the context of Linux clusters.
+The node attribute hana_<sid>_op_mode or cluster attribute hana_<sid>_glob_op_mode is set by SAPHanaTopology, according to the running HANA. The attribute is used by the SAPHanaController or SAPHana resource agent for setting up system replication. In SAPHanaSR-ScaleOut, the cluster attribute is written only if it differs from current value or from RA default "logreplay". In any case, delta_datashipping is not recommended in the context of Linux clusters.
 .PP
 .B remoteHost
 - HANA SR remote host
@@ -303,12 +306,14 @@ Value: [ 4 | 3 | 2 | 1 | 0 ]
 This field contains the return code of landscapHostConfiguration.py. The
 parameter does not tell you if the secondary system is ready for a takeover.
 The meaning is different from common Linux return codes.
+The SAPHanaSR and SAPHanaSR-ScaleOut RAs will interpret return code 1 as
+NOT-RUNNING (or ERROR) and return codes 2+3+4 as RUNNING.
 .br
 4 = OK - Everything looks perfect on the HANA primary.
 .br
-3 = WARNING - A HANA Host Auto-Failover is taking place.
+3 =  INFO - The landscape is completely functional, but the actual host role differs from the configured role.
 .br
-2 = INFO - The landscape is completely functional, but the actual role of the host differs from the configured role.
+2 = WARNING - An internal HANA action is ongoing, e.g. host auto-failover.  
 .br
 1 = DOWN - There are not enough active hosts.
 .br
@@ -379,7 +384,9 @@ Value: [ sync | syncmem ]
 
 The node attribute hana_<sid>_srmode or cluster attribute hana_<sid>_glob_srmode is set by SAPHanaTopology, according to the running HANA.
 The attribute is used by the SAPHanaController or SAPHana resource agent for setting up system
-replication. SAP HANA knows also async and fullsync (see URLs below).
+replication. In SAPHanaSR-ScaleOut, the cluster attribute is written only if it differs from current
+value or from RA default "sync".
+SAP HANA knows also async and fullsync (see URLs below).
 Those do not make sense for automating HANA system replication by an Linux cluster.
 .PP
 .B standby
@@ -577,7 +584,7 @@ F.Herschel, L.Pinne.
 .br
 (c) 2015-2017 SUSE Linux GmbH, Germany.
 .br
-(c) 2018-2022 SUSE LLC
+(c) 2018-2024 SUSE LLC
 .br
 SAPHanaSR-showAttr comes with ABSOLUTELY NO WARRANTY.
 .br

man/SAPHanaSR.7

@@ -1,6 +1,6 @@
 .\" Version: 0.160.1
 .\"
-.TH SAPHanaSR 7 "22 Jun 2022" "" "SAPHanaSR"
+.TH SAPHanaSR 7 "04 Jan 2024" "" "SAPHanaSR"
 .\"
 .SH NAME
 SAPHanaSR \- Tools for automating SAP HANA system replication in scale-up setups.
@@ -181,7 +181,7 @@ left-over migration constraints, and resource failures as well as the HANA
 landscape status, and the HANA SR status.
 .PP
 \fB*\fR Manually activating an HANA primary creates risk of a dual-primary situation.
-The user is responsible for data integrity.
+The user is responsible for data integrity. See also susTkOver.py(7).
 .PP
 .\"
 .SH REQUIREMENTS
@@ -200,7 +200,8 @@ Linux system. If users are resolved by remote service, local caching is
 neccessary. Substitute user (su) to sidadm needs to work reliable and without
 customized actions or messages. Supported shell is bash.
 .PP
-3. Strict time synchronization between the cluster nodes, e.g. NTP.
+3. Strict time synchronization between the cluster nodes, e.g. NTP. All nodes of
+the Linux cluster have configured the same timezone.
 .PP
 4. For scale-up the following SAP HANA SR scenarios are supported with the
 SAPHanaSR package:
@@ -219,13 +220,14 @@ SAPHanaSR package:
 .br
 Note: For MCOS, there must be no constraints between HANA SR pairs.
 .PP
-5. Only one system replication between the two SAP HANA database in the Linux cluster.
+5. Only one system replication between the two SAP HANA databases in the Linux cluster.
 Maximum one system replication to an HANA database outside the Linux cluster.
 See also item 12 below.
 .PP
 6. The replication mode is either sync or syncmem for the controlled replication.
 Replication mode async is not supported. The operation modes delta_datashipping,
-logreplay and logreplay_readaccess are supported.
+logreplay and logreplay_readaccess are supported. The operation mode logreplay
+is default.
 .PP
 7. Both SAP HANA database systems have the same SAP Identifier (SID) and
 Instance Number (INO).
@@ -239,7 +241,7 @@ However, all nodes in one Linux cluster have to use the same style.
 9. Automated start of SAP HANA database systems during system boot must be switched
 off.
 .PP
-10. The RA's monitoring operations have to be active.
+10. The RAs' monitoring operations have to be active.
 .PP
 11. Using HADR provider hook for srConnectionChanged() by enabling SAPHanaSR.py
 is strongly recommended. This might become mandatory in furture versions.
@@ -263,15 +265,16 @@ being written into CIB attributes. The current HANA SR status might differ
 from CIB srHook attribute after cluster maintenance.
 .PP
 15. Once an HANA system replication site is known to the Linux cluster, that
-exact site name has to be used whenever the site is registered manually.
+exact site name has to be used whenever the site is registered manually. At any
+time only one site is configured as primary replication source.
 .PP
 16. Reliable access to the /hana/shared/ filesystem is crucial for HANA and the
 Linux cluster.
 .PP
 17. HANA feature Secondary Time Travel is not supported.
 .PP
 18. In MDC configurations the HANA database is treated as a single system
-including all database containers. Therefore, cluster takeover decisions are
+including all database containers. Therefor, cluster takeover decisions are
 based on the complete status independent of the status of individual containers.
 .PP
 19. If a third HANA site is connected by system replication, that HANA is not
@@ -288,6 +291,17 @@ memory can be used, as long as they are transparent to SUSE HA.
 22. The SAP HANA site name is from 2 up to 32 characters long. It starts with a
 character or number. Subsequent characters may contain dash and underscore.
 .PP
+23. The SAPHanaController RA, the SUSE HA cluster and several SAP components
+need read/write access and sufficient space in the Linux /tmp filesystem.
+.PP
+24. SAP HANA Native Storage Extension (NSE) is supported.
+Important is that this feature does not change the HANA topology or interfaces.
+In opposite to Native Storage Extension, the HANA Extension Nodes are changing
+the topology and thus currently are not supported. 
+Please refer to SAP documentation for details.
+.PP
+25. The Linux user root´s shell is /bin/bash, or completely compatible.
+.PP
 .\"
 .SH BUGS
 .\" TODO
@@ -336,7 +350,7 @@ A.Briel, F.Herschel, L.Pinne.
 .SH COPYRIGHT
 (c) 2015-2018 SUSE Linux GmbH, Germany.
 .br
-(c) 2019-2022 SUSE LLC
+(c) 2019-2024 SUSE LLC
 .br
 The package SAPHanaSR comes with ABSOLUTELY NO WARRANTY.
 .br