Recommended update for saptune

Announcement ID: SUSE-RU-2019:1991-1
Rating: moderate
Affected Products:
  • SUSE Linux Enterprise Server for SAP Applications 12 SP2

An update that has 11 fixes can now be installed.


This update for saptune fixes the following issues:

  • Resetting all values to clean the system during package removal

  • Fix saptune issues with /etc/security/limits.conf. (bsc#1124485)

  • Add deprecated message to the description of some notes set scheduler for note SUSE-GUIDE-01 correctly.(bsc#1123808)

  • Ship both versions of saptune in one package to support a smooth migration controlled by the customer. See man saptune-migrate(5) for more information.

  • Support note name changes and note deletion during update of saptune v2 from SLE12 to SLE15.

  • Support different SAP Note definitions and solution definitions related to the used operation system version (distinguish between SLE12 and SLE15 at the moment)

  • Remove calculation of optimized values, only set the values from the configuration file irrespective of the current system value. Current system value can be increase or decrease. ATTENTION: saptune no longer respects higher system values. Use the override option to change the values of the Note definition files, if needed. (bsc#1124488)

  • Mark the Notes SUSE-GUIDE-01 and SUSE-GUIDE-02 as deprecated in saptune v1 and remove these Note definitions from saptune v2. (bsc#1116799)

  • Add bash-completion for saptune.

  • Add action 'show' to the 'note' operation to print content of the note definition file to stdout.

  • Add new action 'create' to support the customer/vendor while creating a vendor or customer specific file in /etc/saptune/extra using the template file /usr/share/saptune/NoteTemplate.conf

  • Simplify file name syntax for the vendor files available in /etc/saptune/extra. Old file names still valid and supported.

  • Add header support (version, date, description) for the vendor files available in /etc/saptune/extra as already available for the note definition files in /usr/share/saptune/notes

  • No longer write or remove entries from /etc/security/limits.conf. Instead add or remove drop-in files in /etc/security/limits.d The filename syntax for the drop-in files /etc/security/limits.d is saptune-<domain>-<item>-<type>.conf. The limits entry syntax inside the Note definition files changed to support more than one limits settings in the definition file. (bsc#1128322)

  • Preserve comment sections of the security limits file /etc/security/limits.conf. Especially, if this is the only content of the file. (bsc#1124485)

  • Work with the current Note definition file to define the pagecache settings. (bsc#1126220)

  • Setting of UserTaskMax by applying the related SAP Notes in the postinstall of the package. (bsc#1124489)

  • Starting to support severities INFO, WARNING, ERROR and DEBUG for the logging and add a defined format for the log messages.

  • Remove saptune as active tuned profile during action 'saptune daemon stop' - start/stop services, if requested by SAP Notes, but do not enable/disable these services. (bsc#1128325)

  • Adapt the parameter oriented save state file handling (store and revert) to the special needs of the security limits parameter. (bsc#1124485)

  • Disable parameter settings using an override file. (bsc#1124486)

  • Store the order of the note as they are applied to get the same system tuning result after a system reboot as before.

  • Correct the revert of the vm.dirty parameters by handling their counterpart parameters in addition. (bsc#1124487)

  • Adjust operation customize to the new configuration files and override location and enable customize option for vendor and customer specific files in /etc/saptune/extra. (bsc#1124487)

  • Change output format of the operations list, verify and simulate. (bsc#1124487)

  • Display footnotes during 'verify' and 'simulate'. (bsc#1124487)

  • Remove Netweaver formula for page cache calculation. Use the HANA approach '2% system memory' for both.

  • Display a warning message, if a [block] section is found in the Note definition file because on systems with a huge number of block devices this operation may take some time.

  • Add force_latency handling to 'cpu' section. Use the files in /sys/devices/system/cpu/cpu* instead of /dev/cpu_dma_latency. Remove the parameter from the tuned.conf file and add it to the SAP note files '1984787' and '2205917'

  • Add action 'saptune revert all' and add parameter based saved state files to support proper revert functionality. (bsc#1124487)

  • Add override file handling for the solution definition using /etc/saptune/override/solution. (bsc#1124486)

  • Read solution definition from file /usr/share/saptune/solution instead of static coding inside of saptune. (bsc#1124486)

  • Make sure a note, which is part of an applied solution definition, but was reverted manually later, will NOT applied again after a system reboot.

  • One configuration file per SAP Note. (bsc#1124486)

  • Add new SAP Notes and adapt content of SAP Notes.

  • Handle different locations of the new configuration files (/usr/share/saptune/note, /etc/saptune/extra). (bsc#1124486)

  • Allow parameter override by the customer. (bsc#1124486)

  • Expand section handling of the 'ini file' handler to handle the new configuration file entries. Supported sections: version, reminder, login, mem, vm, block, limits, sysctl, pagecache, cpu, service, rpm, grub. (bsc#1124486)

  • Remove new line from println arg list of main.go to support newer go versions. (bsc#1120741)

Patch Instructions:

To install this SUSE 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 Server for SAP Applications 12 SP2
    zypper in -t patch SUSE-SLE-SAP-12-SP2-2019-1991=1

Package List:

  • SUSE Linux Enterprise Server for SAP Applications 12 SP2 (ppc64le x86_64)
    • saptune-debuginfo-2.0.1-8.16.1
    • saptune-2.0.1-8.16.1