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):
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
Old profile used after step 2.
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.
(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.
A fix for this is waiting to be merged upstream. Jardo, can you take a look at it? Thanks!
Dropping needinfo, the fix got merged now.
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.