Back to bug 1385838

Who When What Removed Added
Luiz Capitulino 2016-10-17 19:06:34 UTC Blocks 1240765
Luiz Capitulino 2016-10-17 19:07:57 UTC CC atheurer, krister
Luiz Capitulino 2016-10-17 19:08:15 UTC Summary tuned: no clear indication of profile load error tuned: no clear indication of profile load error during boot
Tereza Cerna 2016-11-29 09:11:26 UTC CC tcerna
Leos Pol 2016-12-05 09:04:10 UTC Blocks 1400961
Leos Pol 2017-07-19 11:01:35 UTC Blocks 1472751
Jaroslav Škarvada 2017-08-09 15:28:46 UTC Status NEW ASSIGNED
Blocks 1467576
Ondřej Lysoněk 2017-08-24 10:50:43 UTC CC olysonek
Doc Type If docs needed, set a value Release Note
Jaroslav Škarvada 2017-08-28 13:58:34 UTC Blocks 1485946
Tereza Cerna 2017-09-07 07:21:26 UTC QA Contact qe-baseos-daemons lcapitulino
Jaroslav Škarvada 2017-10-12 20:44:16 UTC Blocks 1467576
Luiz Capitulino 2017-10-13 13:52:55 UTC Summary tuned: no clear indication of profile load error during boot no clear indication of profile activation error
Lenka Špačková 2017-11-14 10:22:47 UTC Doc Type Release Note Known Issue
Lenka Špačková 2017-11-15 14:11:52 UTC Docs Contact lmanasko
Lucie Vařáková 2017-12-01 13:38:24 UTC Flags needinfo?(jskarvad)
Jaroslav Škarvada 2017-12-01 15:52:10 UTC Doc Text Cause:
Due to the nature of the Tuned service (it's both D-Bus listening daemon and systemd service) the errors in the Tuned configuration or errors occurring when loading Tuned profile(s) may not be shown in the output of the 'systemctl status tuned' command.

Consequence:
If there are errors causing Tuned profile not to load, Tuned can ends in a state with no profile activated. This is indicated by the output of the 'tuned-adm active' command and in the Tuned logs, but not by the 'systemctl status tuned' command, which can be confusing. This is by design and allows Tuned to recover by D-Bus call requesting load of valid Tuned profile (e.g. from Cockpit).

Workaround (if any):
Consult output of 'tuned-adm active' and content of the /var/log/tuned/tuned.log, all errors should be written in the log.

Result:
By checking the logs it should be clear what happened.
Flags needinfo?(jskarvad)
Lucie Vařáková 2018-01-02 14:31:43 UTC Doc Text Cause:
Due to the nature of the Tuned service (it's both D-Bus listening daemon and systemd service) the errors in the Tuned configuration or errors occurring when loading Tuned profile(s) may not be shown in the output of the 'systemctl status tuned' command.

Consequence:
If there are errors causing Tuned profile not to load, Tuned can ends in a state with no profile activated. This is indicated by the output of the 'tuned-adm active' command and in the Tuned logs, but not by the 'systemctl status tuned' command, which can be confusing. This is by design and allows Tuned to recover by D-Bus call requesting load of valid Tuned profile (e.g. from Cockpit).

Workaround (if any):
Consult output of 'tuned-adm active' and content of the /var/log/tuned/tuned.log, all errors should be written in the log.

Result:
By checking the logs it should be clear what happened.
No clear indication of profile activation error in the Tuned service

Due to the nature of the Tuned service, the errors in the Tuned configuration or the errors occurring when loading Tuned profile(s) may not be shown in the output of the "systemctl status tuned" command. As a consequence, if there are errors that prevent Tuned from loading, Tuned can get to a state with no profile activated. To view possible error messages, consult output of the "tuned-adm active" command and check contents of the `/var/log/tuned/tuned.log` file.
Lucie Vařáková 2018-01-02 15:30:44 UTC Doc Text No clear indication of profile activation error in the Tuned service

Due to the nature of the Tuned service, the errors in the Tuned configuration or the errors occurring when loading Tuned profile(s) may not be shown in the output of the "systemctl status tuned" command. As a consequence, if there are errors that prevent Tuned from loading, Tuned can get to a state with no profile activated. To view possible error messages, consult output of the "tuned-adm active" command and check contents of the `/var/log/tuned/tuned.log` file.
No clear indication of profile activation error in the Tuned service

Errors in the Tuned service configuration or errors occurring when loading Tuned profiles are in some cases not shown in the output of the "systemctl status tuned" command. As a consequence, if errors occur that prevent Tuned from loading, Tuned sometimes enters a state with no profile activated. To view possible error messages, consult the output of the "tuned-adm active" command and check the contents of the `/var/log/tuned/tuned.log` file.
Lucie Vařáková 2018-01-02 15:32:23 UTC Flags needinfo?(jskarvad)
Jaroslav Škarvada 2018-01-04 09:40:13 UTC Flags needinfo?(jskarvad)
Pat Riehecky 2018-01-24 16:46:43 UTC CC riehecky
Aaron 2018-08-05 20:53:04 UTC CC aaron_wilk
Jaroslav Škarvada 2018-10-26 21:52:40 UTC Doc Type Known Issue If docs needed, set a value
Jaroslav Škarvada 2019-12-04 15:00:35 UTC Blocks 1779708
Tomáš Hozza 2019-12-18 11:23:20 UTC CC thozza
RHEL Program Management 2019-12-18 11:23:30 UTC Status ASSIGNED CLOSED
Resolution --- WONTFIX
Last Closed 2019-12-18 11:23:30 UTC

Back to bug 1385838