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:
There is a handler for catching SIGHUP in the tuned daemon. The handler reloads the tuned controller, but it does not apply a new profile like a full tuned restart, when invoked by 'systemctl restart tuned' for example. In other words, the signal handler should make sure a new (if any) profile is also applied on SIGHUP.
Version-Release number of selected component (if applicable):
All
How reproducible:
Always
Steps to Reproduce:
1. cd /etc/tuned && echo my-new-profile > active_profile && echo manual > profile_mode
2. pkill -HUP -f tuned
3. tuned-adm profile | grep active # sill shows the old profile
4. systemctl restart tuned # will apply my-new-profile
Actual results:
Old profile used after step 2.
Expected results:
New profile used after step 2.
I tend to agree. I think the SIGHUP handler should have the same effect as doing a Tuned restart. So we need to reload from disk /etc/tuned/active_profile, /etc/tuned/profile_mode, all recommend.conf files and the profile that is to be activated.
Comment 4Jaroslav Škarvada
2018-09-21 16:18:00 UTC
(In reply to Ondřej Lysoněk from comment #3)
> I tend to agree. I think the SIGHUP handler should have the same effect as
> doing a Tuned restart. So we need to reload from disk
> /etc/tuned/active_profile, /etc/tuned/profile_mode, all recommend.conf files
> and the profile that is to be activated.
+1
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, 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-2019:2201