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.

For better integration with VDSM tuned should add a rule to udev or periodically poll it for new devices and change their I/O scheduler according to the current profile.

currently to achieve this we need to change the scheduler in our own code (what happens) or ask tuned to reconfigure (creating unwanted awareness of the tuned package in code)

Hello,

I would phrase that differently.

Operating system is dynamic by nature. Performing tuning at specific point in time can be true for this point in time but this point only.

Doing so at one point in time does not require any daemon to run, as it can do any required tuning and exit.

What I expect is to see a daemon tuning the system when changed based on selected profile, this by [at least] listening to udev events.

I recommend avoiding a [simple] poll loop (even once per minute) as it consume unneeded power and does not meet with the "tune" task.

Thank you,
Alon Bar-Lev.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

AFAIK this is fixed in RHEL-6.4 (tuned-0.2.19-11.el6_4.1 and up) - ktune is restarted by the udev rule when the new block device is added to the system.

Feel free to reopen this bug / comment here if it doesn't resolve the problem for you.