Bug 1254538

Summary:	network-throughput: sysctl tuning are not applied
Product:	Red Hat Enterprise Linux 7	Reporter:	Jaroslav Škarvada <jskarvad>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Tereza Cerna <tcerna>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.2	CC:	jeder, jscotka, jskarvad, ovasik, tcerna
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tuned-2.5.1-3.el7	Doc Type:	Bug Fix
Doc Text:	Cause: Previously, sysctl settings were not unquoted before they were applied. Consequence: Tuned could silently fail to apply the quoted sysctl settings. This was especially problem for the network-throughput profile. In this profile the sysctl settings were specified quoted which resulted in this tuning not being applied. Fix: The Tuned code was improved to unquote sysctl settings before there are applied. Result: Now the sysctl settings are correctly applied.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 12:21:59 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:

Description Jaroslav Škarvada 2015-08-18 10:54:00 UTC

Description of problem:
network-throughput: sysctl tunings are not correctly applied because sysctl commands aren't unquoted.

Version-Release number of selected component (if applicable):
tuned-2.5.1-1.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. tuned-adm profile network-throughput
2. sysctl net.ipv4.tcp_rmem
sysctl net.ipv4.tcp_wmem
sysctl net.ipv4.udp_mem

Actual results:
Settings differ from the profile.

Expected results:
Settings matching the profile.

Additional info:

Comment 1 Jaroslav Škarvada 2015-08-19 12:17:23 UTC

Fixed in upstream commit:
https://git.fedorahosted.org/cgit/tuned.git/commit/?id=efac9c470b2a74da94c92703e87da603bf87296f

Comment 6 errata-xmlrpc 2015-11-19 12:21:59 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-2015-2375.html