Bug 1613950

Summary: Tuned hangs with cpu-partitioning and offlined cpu(s) [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Reznik <jreznik>
Component: tunedAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Tereza Cerna <tcerna>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 7.4CC: jbastian, jeder, jmario, jskarvad, mkolaja, olysonek, salmy, tcerna
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tuned-2.8.0-5.el7_4.3 Doc Type: If docs needed, set a value
Doc Text:
Previously, setting the cpu-partitioning Tuned profile caused the tuned service to become unresponsive if a CPU was set offline. With this update, the problem has been fixed, and tuned no longer hangs after selecting cpu-partitioning when a CPU is offline.
Story Points: ---
Clone Of: 1613478 Environment:
Last Closed: 2018-09-25 20:44:54 UTC Type: ---
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: 1613478    
Bug Blocks:    

Description Jaroslav Reznik 2018-08-08 15:46:45 UTC
This bug has been copied from bug #1613478 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 3 Tereza Cerna 2018-09-04 13:02:40 UTC
The problem mentioned in parent bug description wasn't reproduced on RHEL-7.4. But it is possible to find this problem on this system, because using file /sys/devices/system/cpu/present instead of /sys/devices/system/cpu/online can leads to errors. 

Patch tuned-2.8.0-use-online-cpus.patch was applied in tuned-2.8.0-5.el7_4.3 (prepared package for rhel-7.4.eus in ER#35664). All regression and sanity test cases passed and worked well.

Comment 5 errata-xmlrpc 2018-09-25 20:44:54 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-2018:2774