Bug 1684122

Summary: s2kb function doesn't work with python3
Product: Red Hat Enterprise Linux 8 Reporter: Jaroslav Škarvada <jskarvad>
Component: tunedAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Robin Hack <rhack>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: jeder, jskarvad, olysonek, rhack, tcerna
Target Milestone: rcKeywords: Patch, Regression, Upstream
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tuned-2.12.0-0.1.rc1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:31:10 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 2019-02-28 13:39:59 UTC
Description of problem:
s2kb function is not compatible with python3.

Version-Release number of selected component (if applicable):
tuned-2.10.0-15.el8

How reproducible:
Always

Steps to Reproduce:
1. Create Tuned profile (e.g. my-profile) with the following content:
[sysctl]
kernel.sched_migration_cost_ns=${f:s2kb:50}
2. Activate it, e.g.:
# tuned-adm profile my-profile
3. sysctl kernel.sched_migration_cost_ns

Actual results:
!25

Expected results:
25

Additional info:

Comment 1 Jaroslav Škarvada 2019-02-28 13:43:34 UTC
Fixed by the following upstream commit:
https://github.com/redhat-performance/tuned/commit/18118c28149f073dd81d63b3cdf9e5f21e12e1e5

Comment 3 Tereza Cerna 2019-02-28 13:48:28 UTC
Info for QE:

This bug was appeared also in test case:
/CoreOS/tuned/Sanity/built-in-support-for-unit-conversion
in task "Function s2kb"

Test case should work with a bug fix.

Comment 4 Robin Hack 2019-06-11 08:50:13 UTC
QA_ACK+ RHEL8.1

Comment 8 errata-xmlrpc 2019-11-05 22:31:10 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-2019:3633