Bug 1950164

Summary:	tuned bootloader plugin doesn't support rpm-ostree kargs
Product:	Red Hat Enterprise Linux 8	Reporter:	Ben Breard <bbreard>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Robin Hack <rhack>
Severity:	high	Docs Contact:
Priority:	high
Version:	8.5	CC:	jeder, jskarvad, jzerdik, kabbott, rhack
Target Milestone:	beta	Keywords:	Patch, TestCaseNotNeeded, Triaged, Upstream
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tuned-2.16.0-0.1.rc1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 19:58:58 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 Ben Breard 2021-04-15 23:09:49 UTC

Description of problem:

The cpu-partitioning profile is very relevant to the work we're doing in edge computing, but we cannot use it with RHEL for Edge as the bootloader plugin doesn't support rpm-ostree. Rather than rebuild the grub menu on an rpm system, the plugin would need to pass the options to rpm-ostree kargs --append=KEY=VALUE  and/or --replace=KEY=VALUE=NEWVALUE on an rpm-ostree system. 

 

Version-Release number of selected component (if applicable):
8.5 would be amazing


How reproducible:
100%

Steps to Reproduce:
1. configure isolated_cores in /etc/tuned/cpu-partitioning-variables.conf
2. tuned-adm profile cpu-partitioning
3. 

Actual results:
grub config does not change


Expected results:
apply the config from tuned via rpm-ostree. 

Additional info:
I don't think it would be too difficult to check if the plugin is running on an rpm-ostree system and alter it's behavior accordingly.

Comment 5 Jaroslav Škarvada 2021-07-01 22:37:36 UTC

Upstream PR:
https://github.com/redhat-performance/tuned/pull/359

Comment 10 errata-xmlrpc 2021-11-09 19:58:58 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 (tuned bug fix and enhancement update), 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-2021:4476