Description of problem: A race condition exists between extracting tuned daemon profiles CR into /etc/tuned directory and applying the pre-calculated profile CR. If the pre-calculated profile CR is set and processed prior to the tuned profiles being present in /etc/tuned a possibility exists the calculated profile will not be set. Version-Release number of selected component (if applicable): All 4.4 and 4.5 OCP releases. How reproducible: Rare. Actual results: Failure to set a tuned profile and a message such as: I0311 10:35:52.181745 476886 tuned.go:425] active profile () != recommended profile (openshift-control-plane) I0311 10:35:52.181790 476886 tuned.go:429] tuned profile directory "/etc/tuned/openshift-control-plane" does not exist in the tuned pod logs. Expected results: A profile correctly set. Additional info: A PR to fix this problem: https://github.com/openshift/cluster-node-tuning-operator/pull/117
Verification positive. I was not able to reproduce the issue. Cluster AWS ocp v: 4.5.0-0.nightly-2020-03-17-094857
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-2020:2409