SUSE-FU-2021:3483-1: moderate: Feature update for saptune

sle-updates at sle-updates at
Wed Oct 20 19:23:42 UTC 2021

   SUSE Feature Update: Feature update for saptune

Announcement ID:    SUSE-FU-2021:3483-1
Rating:             moderate
References:         #1149205 #1164720 #1167213 #1167416 #1167618 
                    #1170672 #1176243 #1178207 #1179275 #1182009 
                    #1182287 #1182289 #1185702 SLE-10823 SLE-10842 
                    SLE-13245 SLE-13246 SLE-16972 SLE-20985 SLE-5588 
                    SLE-5589 SLE-6457 TEAM-1679 TEAM-1696 TEAM-1699 
                    TEAM-1700 TEAM-1701 TEAM-1702 TEAM-1705 TEAM-1706 
                    TEAM-1707 TEAM-1728 TEAM-1754 TEAM-1755 TEAM-1844 
                    TEAM-2675 TEAM-2676 TEAM-3154 TEAM-3342 TEAM-3454 
                    TEAM-4093 TEAM-4260 TEAM-4386 TEAM-825 
Affected Products:
                    SUSE Linux Enterprise Module for SAP Applications 15-SP3
                    SUSE Linux Enterprise Module for SAP Applications 15-SP2
                    SUSE Linux Enterprise Module for SAP Applications 15-SP1

   An update that has 13 feature fixes and contains 31
   features can now be installed.


   This update for saptune fixes the following issues:

   Update saptune from version 2.0.3 to version 3.0.0 (jsc#SLE-20985)

   - This will be additional reflected in the saptune version found in
     '/etc/sysconfig/saptune' '(SAPTUNE_VERSION)'
   - Strengthen configuration process with staging, checks of external
     changes and expansion of automation to new platforms (Azure, AWS) and
     hardware specifics (jsc#SLE-20985)
   - Remove saptune version 1 (jsc#SLE-10823, jsc#SLE-10842)
   - Remove usage of 'tuned' from saptune
     - Add an own systemd service file for saptune to 'start/stop' tuning of
       parameter values during a reboot of the system.
     - Add a new saptune action 'service' to handle the 'saptune.service'
       supporting 'start/stop/enable/disable/status'.
     - The saptune action 'daemon', which handled 'tuned.service' in the
       past, is now flagged as 'deprecated' and internally linked to the new
       action 'service'. (jsc#SLE-5589, jsc#SLE-5588, jsc#SLE-6457)
   - Add a sanity check to detect Note definition files which do not exist
     anymore. (bsc#1149205) This can happen when a Note is renamed or
     deleted, but without reverting the Note before. saptune will now print
     an error message, remove the Note from the tracking variables in
     '/etc/sysconfig/saptune' and try to revert the related parameter
   - Validate if the json input file is empty and handle left-over files from
     the migration from saptune v1 to saptune v2 (bsc#1167618)
   - To support system parameters only relevant for specific SUSE Linux
     Enterprise Server releases, service packs and/or hardware architectures
     saptune now supports 'tagged' sections inside the Note definition files.
     (jsc#SLE-13246, jsc#SLE-13245)
   - New kernel requirement for Power added to SAP-Note 2205917 and 2684254
     (bsc#1167416) SAP Note 2205917 updated to Version 61 SAP Note 2684254
     updated to Version 15
   - SAP Note 2382421 updated to Version 37 (bsc#1170672)
     - Move all 'not-well-defined' parameters from the 'reminder' section
       into the 'sysctl' section, but with 'empty' values.
     - Use an override file to define the values fitting your system
   - Support empty parameter values in the Note definition files and not only
     in the override file. (bsc#1170672, jsc#TEAM-1702)
     - This is needed for the support of SAP Notes like 2382421, so that the
       customer is able to simply use an override file to define some special
       parameters instead of using a customer specific Note definition file.
   - Report an 'error' instead of 'info' and set the exit code to '1', if we
     reject the apply of a solution (bsc#1167213)
   - Skip perf bias change if secure boot is enabled. (bsc#1176243)
     - When a system is in lockdown mode, i.e., Secure Boot is enabled, MSR
       cannot be altered in user-space. So check, if Secure Boot is enabled
       using the mokutil utility and skip setting the perf bias in case it is.
   - Rework the internal block device handling to speed up the apply of block
     device related tunings on systems with a high number of block devices.
   - Change block device handling to handle multipath devices correctly. Only
     the DM multipath devices will be used for the settings, but not its
     paths. (bsc#1179275)
   - fixed wrong comparison used for setting FORCE_LATENCY (bsc#1185702)
   - add keyword 'all' to the 'rpm' section description in the man page
     saptune-note(5). (bsc#1182287)
   - support note definition versions containing digits, upper-case and
     lower-case letters, dots, underscores, minus and plus signs.
   - fixed issue with 'verify' operation and parameter 'VSZ_TMPFS_PERCENT'.
     As this parameter is only used to calculate the value of
     'ShmFileSystemSizeMB' (if it is not set to a value >0 in the Note
     definition file) it will not be checked and compared during the saptune
     operation 'verify'. A footnote is pointing this out.  (bsc#1182009)
   - SAP Note 1771258 update nofile values (bsc#1164720)
   - SAP Note 2684254 updated to Version 20 SAP Note 2578899 updated to
     Version 39 SAP Note 1680803 updated to Version 26
   - enhancements for saptune version 3 (jsc#SLE-16972)
     - Implement a lock to avoid multiple instances of saptune running in
       parallel. (jsc#TEAM-1700)
     - Support for non-colorized output (jsc#TEAM-1679)
     - If redirecting the output from saptune to a pipe, you no longer need
       to deal with the 'ugly' control sequences for the colorized output.
     - Add enable/disable for systemd units and support all systemd unit
       types in section [service] (jsc#TEAM-1701)
     - remove script '/usr/share/doc/packages/saptune/sapconf2saptune' and
       the associated man page (jsc#TEAM-1707)
     - implement staging of Note definition file and solution definitions.
       - The idea is to freeze the saptune configuration to avoid config
         changes on package update when adding/removing/changing notes or
         solutions within the package
     - support custom solutions and override files for solutions.
       - Partners and customers will now be able to define their own solution
         definitions by using files in '/etc/saptune/extra' or to override
         the shipped solution definitions by using override files in
     - support for device specific configurations (jsc#TEAM-1728)
       - only supported for the [block] section, tags are 'vendor' and
         'model' to support special block devices
       of a dedicated hardware vendor or a dedicated hardware model
     - add support for AZURE cloud (SAP Note 2993054) (jsc#TEAM-2676)
     - add support for AWS cloud (SAP Note 1656250) (jsc#TEAM-1754,
     - add NVMe support to the block device handling to support AWS
     - add SAP Note 3024346 (a NetApp note) (jsc#TEAM-3454)
     - rework daemon and service actions (jsc#TEAM-3154)
     - add support for 'read_ahead_kb' and 'max_sectors_kb' to the [block]
       section (jsc#TEAM-1699)
     - add a warning to the reminder section of SAP Note 2382421 regarding
       iSCSI devices and setting of 'net.ipv4.tcp_syn_retries' (jsc#TEAM-1705)
     - For the actions 'note customise' and 'note create' check, if the
       customer has changed something during the editor session. If not,
       remove the temporary created note definition file. (jsc#TEAM-825)
     - add support for [sys] section and handle double configurations for
       parameters defined in the [sys] section (jsc#TEAM-3342)
     - check system sysctl config files as mentioned in the comments of
       '/etc/sysctl.conf' and in man page 'sysctl.conf(5)' for 'sysctl'
       parameters currently set by saptune notes. Print a warning and a
       footnote for 'verify' and 'customize'. (jsc#TEAM-1696)
     - add support for [filesystem] section only check filesystem mount
       options, not modify. Starting with filesystem type 'xfs'
     - add SAP Note 900929 for SAP Netweaver workloads. (jsc#TEAM-4386)
       - It's the equivalent to the HANA Note 1980196.
     - move state files from '/var/lib/saptune' to '/run/saptune' to solve
       the problem of state files surviving a reboot.
     - add '/sbin/saptune_check'
     - add the description of the solution definitions shipped with saptune
       to the man page saptune(8) (jsc#TEAM-4260)

Patch Instructions:

   To install this SUSE Feature Update use the SUSE recommended installation methods
   like YaST online_update or "zypper patch".

   Alternatively you can run the command listed for your product:

   - SUSE Linux Enterprise Module for SAP Applications 15-SP3:

      zypper in -t patch SUSE-SLE-Module-SAP-Applications-15-SP3-2021-3483=1

   - SUSE Linux Enterprise Module for SAP Applications 15-SP2:

      zypper in -t patch SUSE-SLE-Module-SAP-Applications-15-SP2-2021-3483=1

   - SUSE Linux Enterprise Module for SAP Applications 15-SP1:

      zypper in -t patch SUSE-SLE-Module-SAP-Applications-15-SP1-2021-3483=1

Package List:

   - SUSE Linux Enterprise Module for SAP Applications 15-SP3 (ppc64le x86_64):


   - SUSE Linux Enterprise Module for SAP Applications 15-SP2 (ppc64le x86_64):


   - SUSE Linux Enterprise Module for SAP Applications 15-SP1 (ppc64le x86_64):



More information about the sle-updates mailing list