Bug 1788195

Summary:	The [scheduler] plug-in should write into /etc/systemd/system.conf.d/ instead of modifying /etc/systemd/system.conf
Product:	Red Hat Enterprise Linux 8	Reporter:	Jaroslav Škarvada <jskarvad>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.6	CC:	jeder, jmencak, jskarvad, qe-baseos-daemons
Target Milestone:	rc	Keywords:	Reopened, Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1783336	Environment:
Last Closed:	2023-07-08 07:27: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:
Bug Depends On:	1783336
Bug Blocks:

Description Jaroslav Škarvada 2020-01-06 16:46:09 UTC

+++ This bug was initially created as a clone of Bug #1783336 +++

Description of problem:
In general, drop-in configuration files should be used whenever possible.  This reduces the contention and a need for locks when two or more processes are trying to write to a shared configuration file.  The tuned daemon's [scheduler] plugin writes settings (CPUAffinity) into /etc/systemd/system.conf.  I suggest creating something like /etc/systemd/system.conf.d/50-tuned.conf instead.

Version-Release number of selected component (if applicable):
All

How reproducible:
Always

Steps to Reproduce:
1. Use tuned's [scheduler] plugin or look in the tuned's current code.

Actual results:
/etc/systemd/system.conf modified.

Expected results:
A configuration file in /etc/systemd/system.conf.d/ written.

Additional info:
This is mostly a problem when running containerized tuned on RHCOS, where there are limited number of modifications a container can do on the host without causing potential issues.

--- Additional comment from RHEL Program Management on 2019-12-13 16:24:01 CET ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

Comment 3 RHEL Program Management 2021-07-06 07:30:17 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 4 Jiří Mencák 2021-07-08 10:38:57 UTC

This bug is still relevant, reopenning.

Comment 7 RHEL Program Management 2022-01-08 07:26:59 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 Jiří Mencák 2022-01-08 08:12:10 UTC

This should be a very simple fix and is needed for OCP deployments with containerized TuneD.  Reopenning.

Comment 11 RHEL Program Management 2023-07-08 07:27:58 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.