Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1313489

Summary:	tuned restart temporarily resets ktune settings
Product:	Red Hat Enterprise Linux 6	Reporter:	Julio Entrena Perez <jentrena>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Tereza Cerna <tcerna>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.8	CC:	cww, jeder, jskarvad, psklenar, tcerna, thozza
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	tuned-0.2.19-18.el6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 11:21:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1172231, 1269194, 1359261

Description Julio Entrena Perez 2016-03-01 16:58:16 UTC

Description of problem:
Due to file /lib/udev/tuned-request-ktune-restart sending a USR2 signal to tuned process on device events, settings in <profile_name>/ktune.sh are momentarily reverted to their defaults before being re-applied again.

For example, when a VM is started on a RHEV host the LVM logical volume(s) for that VM are activated, which results in performance CPU governor being disabled and then enabled back again.

Version-Release number of selected component (if applicable):
tuned-0.2.19-16.el6

How reproducible:
Always

Steps to Reproduce:
1. Start a RHEV VM on that host (or just issue "service ktune condrestart" to simulate the same behaviour).
2. Wait 10 seconds after starting the VM (no need to wait for "service ktune condrestart").
3.

Actual results:
In /var/log/tuned/tuned.log :
2016-02-29 11:18:07,434 INFO     tuned: performing ktune conditional restart

In /var/log/messages :
Feb 29 11:18:07 rhevh1-375 cpuspeed: Disabling performance cpu frequency scaling governor
Feb 29 11:18:08 rhevh1-375 cpuspeed: Enabling performance cpu frequency scaling governor


Expected results:
performance cpu governor is not temporarily disabled.

Additional info:
This is a continuation of bug 1111416, where settings in <profile_name>/sysctl.ktune are preserved on stop / restart.
The same is needed for settings in <profile_name>/ktune.sh .

Comment 5 Tereza Cerna 2016-11-29 10:42:25 UTC

This bug is Ok. Switch to status VERIFIED.

Comment 6 Jaroslav Škarvada 2016-11-29 13:26:16 UTC

While the proposed patch fixed Tuned and it behaves now correctly, it seems there is still problem with the 'cpuspeed' package which is used by Tuned.

I checked cpuspeed code and it seems when it writes:
Disabling GOVERNOR cpu frequency scaling governor

It reverts governor to the 'userspace' for all CPUs if acpi-cpufreq scaling driver is used or to the 'powersave' if intel_pstate driver is used. Then immediately it sets the governor which is requested (e.g. performance), i.e. the following:
Nov 25 05:37:13 hp-dl120gen9-01 cpuspeed: Disabling performance cpu frequency scaling governor
Nov 25 05:37:13 hp-dl120gen9-01 cpuspeed: Enabling performance cpu frequency scaling governor

Is also bad as it will probably also cause spike.

We can either:

a) fix cpuspeed
b) drop cpuspeed from Tuned

Regarding b) Tuned already knows how to set the governor through the sysfs and uses this method as a backup if cpuspeed is not installed.

Comment 7 Tereza Cerna 2016-11-29 13:32:16 UTC

Problem with cpuspeed was found. Switch this bug to ASSIGNED.

Comment 9 Tereza Cerna 2016-12-07 09:37:31 UTC

Verified that governor is not switched to another state and then back again. Behaves as expected.

Fixed in tuned-0.2.19-18.el6.noarch

Comment 11 errata-xmlrpc 2017-03-21 11:21:41 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://rhn.redhat.com/errata/RHBA-2017-0738.html