Bug 1854302 - Document the '[modules]' plugin.
Summary: Document the '[modules]' plugin.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tuned
Version: 8.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.4
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-07 07:04 UTC by Jiří Mencák
Modified: 2023-07-07 07:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-07 07:28:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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