Bug 2137299
| Summary: | RFE: User-configured modification of system boot-related files | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jiří Mencák <jmencak> |
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED MIGRATED | QA Contact: | Robin Hack <rhack> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 9.2 | CC: | jeder, jskarvad |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| 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-09-21 21:07:29 UTC | Type: | Story |
| 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
2022-10-24 11:35:37 UTC
Jiri do you need /etc/tuned/bootcmdline for anything? Because if not I would propose more flexible approach allowing global disablement of the plugins through the tuned-main.conf, e.g.: plugins_disabled = bootloader This would globally disable any usage of the bootloader plugin in the TuneD profiles with INFO message that the plugin is disabled. Moreover this approach would allow global disabling of any combination of plugins, e.g. plugins_disabled = bootloader, scheduler Thank you for lookingn into this, Jardo! (In reply to Jaroslav Škarvada from comment #2) > Jiri do you need /etc/tuned/bootcmdline for anything? Because if not I would > propose more flexible approach allowing global disablement of the plugins > through the tuned-main.conf, e.g.: > plugins_disabled = bootloader Yes, we do need and use /etc/tuned/bootcmdline file in RHOCP. What we do at the moment is run TuneD in a container which discards all the modifications TuneD does to the host filesystem (there are some exceptions though). However, we do use /etc/tuned/bootcmdline file to to gather the calculated kernel parameters. That information is then fed as configuration to another RHOCP operator (MCO) which then adjusts the kernel parameters and reboots the host machine. The reasoning behind this request is that the plan is to run TuneD outside of the container directly on the host and we need to disable any conflicting changes on the host filesystem TuneD does while keeping the useful stuff such as calculating the kernel boot parameters in its own directory (/etc/tuned). Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |