RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1672213 - tuned profile sap-hana-vmware retirement
Summary: tuned profile sap-hana-vmware retirement
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned
Version: 7.7-Alt
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Robin Hack
Marie Hornickova
URL:
Whiteboard:
Depends On:
Blocks: 1709724 1715541 1716960 1754591
TreeView+ depends on / blocked
 
Reported: 2019-02-04 09:49 UTC by Rolf Rueck
Modified: 2020-03-31 19:12 UTC (History)
7 users (show)

Fixed In Version: tuned-2.11.0-6.el7
Doc Type: Deprecated Functionality
Doc Text:
.The `sap-hana-vmware` *Tuned* profile has been deprecated The `sap-hana-vmware` *Tuned* profile has been deprecated. For backward compatibility, this profile is still provided in the `tuned-profiles-sap-hana` package, but the profile will be removed in future major release of Red Hat Enterprise Linux. The recommended replacement is the `sap-hana`*Tuned* profile.
Clone Of:
: 1715541 (view as bug list)
Environment:
Last Closed: 2020-03-31 19:12:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1008 0 None None None 2020-03-31 19:12:38 UTC

Description Rolf Rueck 2019-02-04 09:49:42 UTC 
Description of problem:

The tuned profile sap-hana-vmware does only provide two additional parameters to the sap-hana profile which it is based on.

Disables LRO is only recommended on special situations and needs to be set by hand to the correct network interface, before it takes effect.

vm.swappiness is outdated and no longer in sync with best practices from a VMware side.

As such the profile does not provide any benefit for customers.

Actual results:

sap-hana-vmware profile provided


Expected results:

sap-hana profile used instead

Additional info:

A additional bugzilla will be raised for change in insights rules.
Comment 2 Jaroslav Škarvada 2019-02-07 10:26:54 UTC 
(In reply to Rolf Rueck from comment #0)
Are there best practices we could use for it?  If not, I still would keep this profile for RHEL-7 not to cause regression - low benefit or no benefit (this is arguable regarding the LRO tuning) is not argument to remove something from the stable release. We could drop it for next RHEL releases.
Comment 3 Rolf Rueck 2019-02-07 11:27:02 UTC 
(In reply to Jaroslav Škarvada from comment #2)
> (In reply to Rolf Rueck from comment #0)
> Are there best practices we could use for it?  If not, I still would keep
> this profile for RHEL-7 not to cause regression - low benefit or no benefit
> (this is arguable regarding the LRO tuning) is not argument to remove
> something from the stable release. We could drop it for next RHEL releases.

Non that I am aware of. The SAP HANA relevant parameters are already part of the sap-hana profile, which is part of the sap-hana-vmware.

This profile is advised from Insights as the profile to be used with SAP HANA on VMWare. This violates the recommendations of SAP and VMWare regarding what parameters should be used on a system.
Customer are complaining (rightfull) about this.

If we only remove the offending parameter vm.swappiness, the profile is useless, as the LRO tuning requires the administrator to active configure a file with the network interface. It is not recommended to deploy this on all interfaces.

If removing it is not possible, I would like to have it marked deprecated, so that customers are not advised to use it any more.
Comment 4 Jaroslav Škarvada 2019-02-07 15:55:07 UTC 
(In reply to Rolf Rueck from comment #3)
> (In reply to Jaroslav Škarvada from comment #2)
> > (In reply to Rolf Rueck from comment #0)
> > Are there best practices we could use for it?  If not, I still would keep
> > this profile for RHEL-7 not to cause regression - low benefit or no benefit
> > (this is arguable regarding the LRO tuning) is not argument to remove
> > something from the stable release. We could drop it for next RHEL releases.
> 
> Non that I am aware of. The SAP HANA relevant parameters are already part of
> the sap-hana profile, which is part of the sap-hana-vmware.
> 
> This profile is advised from Insights as the profile to be used with SAP
> HANA on VMWare. This violates the recommendations of SAP and VMWare
> regarding what parameters should be used on a system.
> Customer are complaining (rightfull) about this.
> 
> If we only remove the offending parameter vm.swappiness, the profile is
> useless, as the LRO tuning requires the administrator to active configure a
> file with the network interface. It is not recommended to deploy this on all
> interfaces.
> 
> If removing it is not possible, I would like to have it marked deprecated,
> so that customers are not advised to use it any more.

OK, no problem with deprecation for RHEL-7 and we can drop the profile upstream.
Comment 5 Travis Gummels 2019-05-22 17:35:18 UTC 
Jaroslav,

Are you planning to deprecate sap-hana-vmware via this bug or another?  This bug has no acks so it is not on the radar for getting completed in 7.7.

Travis
Comment 6 Jaroslav Škarvada 2019-05-23 08:41:04 UTC 
(In reply to Travis Gummels from comment #5)
> Jaroslav,
> 
> Are you planning to deprecate sap-hana-vmware via this bug or another?  This
> bug has no acks so it is not on the radar for getting completed in 7.7.
> 
> Travis

For RHEL-7 we are going to mark it as deprecated (we will used this BZ for it) and drop in RHEL-8 as discussed earlier in this bugzilla.
Comment 18 errata-xmlrpc 2020-03-31 19:12:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1008
Note You need to log in before you can comment on or make changes to this bug.