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.
+++ This bug was initially created as a clone of Bug #1544030 +++
Description of problem:
tuned cpu-partitioning profile will configure affinity corese if values are quoted
Test in a lab:
~~~
[root@overcloud-compute-0 pcm]# grep -i isol /etc/tuned/cpu-partitioning-variables.conf
# isolated_cores=2,4-7
# isolated_cores=2-23
isolated_cores=2,4,6,8,10,12,14,16,18,22,24,26,28,30,32,34,36,38,3,5,7,9,11,13,15,17,19,23,25,27,29,31,33,35,37,39
[root@overcloud-compute-0 pcm]# grep -i affini /etc/systemd/system.conf
#CPUAffinity=1 2
CPUAffinity=0 1 20 21
~~~
~~~
[root@overcloud-compute-0 pcm]# vi /etc/tuned/cpu-partitioning-variables.conf
[root@overcloud-compute-0 pcm]# grep -i isol /etc/tuned/cpu-partitioning-variables.conf
# isolated_cores=2,4-7
# isolated_cores=2-23
isolated_cores='2,4,6,8,10,12,14,16,18,22,24,26,28,30,32,34,36,38,3,5,7,9,11,13,15,17,19,23,25,27,29,31,33,35,37,39'
[root@overcloud-compute-0 pcm]# tuned-adm profile cpu-partitioning
[root@overcloud-compute-0 pcm]# grep -i affini /etc/systemd/system.conf
#CPUAffinity=1 2
CPUAffinity=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
~~~
~~~
[root@overcloud-compute-0 pcm]# vi /etc/tuned/cpu-partitioning-variables.conf
[root@overcloud-compute-0 pcm]# grep -i isol /etc/tuned/cpu-partitioning-variables.conf
# isolated_cores=2,4-7
# isolated_cores=2-23
isolated_cores=2,4,6,8,10,12,14,16,18,22,24,26,28,30,32,34,36,38,3,5,7,9,11,13,15,17,19,23,25,27,29,31,33,35,37,39
[root@overcloud-compute-0 pcm]# tuned-adm profile cpu-partitioning
[root@overcloud-compute-0 pcm]#
[root@overcloud-compute-0 pcm]# grep -i affini /etc/systemd/system.conf
#CPUAffinity=1 2
CPUAffinity=0 1 20 21
~~~
Can we make this a bit more fool proof and accept quoted core lists?
Thanks,
Andreas
--- Additional comment from atelang on 2018-04-04 22:58:02 EDT ---
From our BZ triage, this seems like we need doc that says " Do not edit/change the isolated_cores or other values directly modified by TripleO in the file /etc/tuned/cpu-partitioning-variables.conf"
(...)
Hi,
The intention of this bug was not to close this within the documentation component.
It's a bug that tuned cpu-partitioning profile does accept values that are quoted and then misconfigures the core isolation on the entire OS.
Either cpu-partitioning should be able to understand values that are put in quotes, or it should fail. It shouldn't misconfigure the entire OS just because an administrator inserts the core list in single quotes.
- Andreas
--- Additional comment from Andreas Karis on 2018-07-13 15:35:56 EDT ---
tuned and cpu-partitioning are standalone components that customers can use without tripleo, so I'd expect the cpu-partitioning tuned profile to catch these kinds of syntax errors and handle them with an error or by being less strict on the requires syntax.
If we decide to allow the quotes, it needs to be carefully considered. The solution needs to be generic, it needs to work the same for all plugins and options. We also need properly specify the semantics, for example is there/can there be a difference between the following:
option_foo="abc def ghi"
vs.
option_foo="abc def" "ghi"
Hi,
If we allow them or not, and regardless of the semantics, cpu-partitioning should fail if the semantics aren't met. I think that's my biggest concern at the moment.
- Andreas
(In reply to Andreas Karis from comment #3)
> Hi,
>
> If we allow them or not, and regardless of the semantics, cpu-partitioning
> should fail if the semantics aren't met. I think that's my biggest concern
> at the moment.
Absolutely. I'm just trying to think of the best solution for the future, while we're at it.
Red Hat Enterprise Linux version 7 entered the Maintenance Support 1 Phase in August 2019. In this phase only qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. Other errata advisories may be delivered as appropriate.
This bug has been reviewed by Support and Engineering representative and does not meet the inclusion criteria for Maintenance Support 1 Phase. If this issue still exists in newer major version of Red Hat Enterprise Linux, it has been cloned there and work will continue in the cloned bug.
For more information about Red Hat Enterprise Linux Lifecycle, please see https://access.redhat.com/support/policy/updates/errata/
Comment 7RHEL Program Management
2019-12-06 16:06:49 UTC
Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain the issue receives the proper prioritization with product and development management.
https://www.redhat.com/support/process/production/#howto