Bug 1854302

Summary:	Document the '[modules]' plugin.
Product:	Red Hat Enterprise Linux 8	Reporter:	Jiří Mencák <jmencak>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	jeder, jskarvad
Target Milestone:	rc	Keywords:	Documentation, Reopened, Triaged
Target Release:	8.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-07 07:28:08 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 Jiří Mencák 2020-07-07 07:04:03 UTC

Description of problem:
There is no documentation for the tuned [modules] plugin as far as I can see apart from sparse information in BZs.  I've seen users typicaly expect that tuned profile specs such as:

[modules]
fuse=

load the fuse module.  However, this is not the case.  In my case, the following was needed

[modules]
fuse=+r

Unfortunately, I was unable to find this in tuned docs.

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

How reproducible:
Always

Actual results:
Tuned [modules] plugin is not documented.

Expected results:
Tuned [modules] plugin is documented.  Differences between using the "reload" functionality vs. the regular

[modules]
fuse=

without reload (+r) described.

Comment 3 RHEL Program Management 2022-01-07 07:27:05 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 2022-01-07 19:10:32 UTC

Reopenning.  Upstream documentation for this is here: https://github.com/redhat-performance/tuned/pull/337/

Comment 7 RHEL Program Management 2023-07-07 07:28:08 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.