SUSE-RU-2024:0787-1: Recommended update for saptune
This update for saptune fixes the following issues: saptune was updated from version 3.1.1 to 3.1.2:
To support setups with saptune monitoring and heavy automation we limited the setting of our saptune lock to commands having the potential to change anything in the system. (bsc#1219500)
Fixed timestamp in log messages of saptune Removed redundant version information in header comment of note definition files SAP Note 1656250 updated to Version 63 SAP Note 1771258 updated to Version 8 SAP Note 2382421 updated to Version 45 SAP Note 3024346 updated to Version 10 but without parameter value changes, only house keeping of the version section and comment updates
SAP Note 1984787 updated to Version 42 SAP Note 2578899 updated to Version 47
Added requirement of package sysctl-logger (jsc#PED-5025)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
suse/saptuneto a version that resolves this vulnerability.Fixed in 3.1.2-4.21.1 - Upgrade
Upgrade
suse/saptune-debuginfoto a version that resolves this vulnerability.Fixed in 3.1.2-4.21.1 - Upgrade
Upgrade
saptuneto a version that resolves this vulnerability.Fixed in 3.1.2Patch SUSE-SLE-SAP-12-SP5-2024-787=1
Event History
Frequently Asked Questions
Which systems are affected by this update?
The update applies to SUSE Linux Enterprise Server for SAP Applications 12 SP5 on ppc64le and x86_64 where the saptune, saptune-debuginfo, or related saptune packages are installed.
What operational issue does the update address?
It limits saptune lock usage to commands that can change the system. This is intended to better support environments that use saptune monitoring alongside heavy automation.
Are there new package dependencies to account for?
Yes. The updated saptune package requires sysctl-logger, so package management and deployment processes must be able to install that dependency.