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 1742209 - tuned-adm cpu-partitioning profile fails when removing cores
Summary: tuned-adm cpu-partitioning profile fails when removing cores
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tuned
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.1
Assignee: Jaroslav Škarvada
QA Contact: Robin Hack
URL: https://bugzilla.redhat.com/show_bug....
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-16 16:34 UTC by Christian Trautman
Modified: 2020-11-14 06:45 UTC (History)
6 users (show)

Fixed In Version: tuned-2.12.0-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:31:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-performance tuned pull 183 0 'None' closed functions: Return an ordered cpu list in cpulist_online 2021-02-10 12:58:04 UTC
Red Hat Product Errata RHBA-2019:3633 0 None None None 2019-11-05 22:31:25 UTC

Description Christian Trautman 2019-08-16 16:34:35 UTC
Description of problem: Unable to set less cores when using cpu-partitioning profile. Reports error 

Cannot load profile(s) 'cpu-partitioning': Assertion 'isolated_cores contains online CPU(s)' failed.


Version-Release number of selected component (if applicable):
RHEL 8.0 kernel version 
4.18.0-80.el8.x86_64
tuned-profiles-cpu-partitioning-2.10.0-15.el8.noarch

How reproducible:
Can reproduce every time on my system

Steps to Reproduce:
1. Fresh install of 8.0 on x86 system
2. yum install -y tuned-profiles-cpu-partitioning
3. Set /etc/tuned/cpu-partitioning.conf file to isolated cores of everything on numa 1.  In my case its 1,3,5,7,9,13,15
4. Reboot
5. After reboot change conf file to use isolated cores of 3,5,7,9
6. Try to apply profile and it will fail with the above error.

Actual results:
Fails 
Cannot load profile(s) 'cpu-partitioning': Assertion 'isolated_cores contains online CPU(s)' failed.

Expected results:
Should apply profile correctly

Additional info:
tuned log shows this error ->

tuned.profiles.functions.function_assertion: assertion 'isolated_cores contains online CPU(s)' failed: '3,5,7,9' != '9,3,5,7'

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


Note You need to log in before you can comment on or make changes to this bug.