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.
Description of problem:
man tuned-adm just mentions one possible argument to option "profile". However, it is possible to specify more than one profile, causing settings from previous profiles to be replaced by settings from further profiles.
Version-Release number of selected component (if applicable):
tuned-2.10.0-14.el8.noarch, tuned-2.13.0-1.el8.noarch
How reproducible:
always
Steps to Reproduce:
1. man tuned-adm
2. Check the contents of sections SYNOPSIS and OPTIONS
3. Confirm that there is just one argument mentioned to option "profile"
Actual results:
SYNOPSIS
tuned-adm [list | active | profile [profile] | off | verify | recommend]
active Show current active profile.
...
OPTIONS
...
profile [PROFILE_NAME]
Switches to the given profile. If none is given then all
available profiles are listed. If the profile given is not valid
the command gracefully exits without performing any operation.
Expected results:
SYNOPSIS
tuned-adm [list | active | profile [profile]... | off | verify |
recommend]
active Show current active profile(s).
...
OPTIONS
...
profile [PROFILE_NAME]...
Switches to the given profile(s). If none is given then all
available profiles are listed. If more than one profile is
provided, settings in all these profiles are used and
settings in the additional profiles replace those from former
ones if present. If the profiles given are not valid, the command
gracefully exits without performing any operation.
Additional info:
More changes in other sections might be necessary, for example in section verify.
(In reply to Ondřej Lysoněk from comment #1)
> Thanks for the report.
>
> Upstream PR:
> https://github.com/redhat-performance/tuned/pull/242
The proposed text in line 67 and 68 does not explain which one of the settings wins in case there are different settings for the same parameter(s) in two or more profiles. I suggest to explain this as well.
Just merging does not mean that the last one wins, or is that a common understanding of "merged" in this context?
(In reply to Bernd Finger from comment #2)
> (In reply to Ondřej Lysoněk from comment #1)
> > Thanks for the report.
> >
> > Upstream PR:
> > https://github.com/redhat-performance/tuned/pull/242
>
> The proposed text in line 67 and 68 does not explain which one of the
> settings wins in case there are different settings for the same parameter(s)
> in two or more profiles. I suggest to explain this as well.
> Just merging does not mean that the last one wins, or is that a common
> understanding of "merged" in this context?
I've updated the PR.
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-2020:4559
Description of problem: man tuned-adm just mentions one possible argument to option "profile". However, it is possible to specify more than one profile, causing settings from previous profiles to be replaced by settings from further profiles. Version-Release number of selected component (if applicable): tuned-2.10.0-14.el8.noarch, tuned-2.13.0-1.el8.noarch How reproducible: always Steps to Reproduce: 1. man tuned-adm 2. Check the contents of sections SYNOPSIS and OPTIONS 3. Confirm that there is just one argument mentioned to option "profile" Actual results: SYNOPSIS tuned-adm [list | active | profile [profile] | off | verify | recommend] active Show current active profile. ... OPTIONS ... profile [PROFILE_NAME] Switches to the given profile. If none is given then all available profiles are listed. If the profile given is not valid the command gracefully exits without performing any operation. Expected results: SYNOPSIS tuned-adm [list | active | profile [profile]... | off | verify | recommend] active Show current active profile(s). ... OPTIONS ... profile [PROFILE_NAME]... Switches to the given profile(s). If none is given then all available profiles are listed. If more than one profile is provided, settings in all these profiles are used and settings in the additional profiles replace those from former ones if present. If the profiles given are not valid, the command gracefully exits without performing any operation. Additional info: More changes in other sections might be necessary, for example in section verify.