Bug 1812605

Summary:	openshift-tuned can fail to set a profile due to a race condition
Product:	OpenShift Container Platform	Reporter:	Jiří Mencák <jmencak>
Component:	Node Tuning Operator	Assignee:	Jiří Mencák <jmencak>
Status:	CLOSED ERRATA	QA Contact:	Simon <skordas>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	sejug
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1814400 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:19:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1814400

Description Jiří Mencák 2020-03-11 16:50:08 UTC

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

Comment 3 Simon 2020-03-17 18:34:20 UTC

Verification positive.
I was not able to reproduce the issue.
Cluster AWS
ocp v: 4.5.0-0.nightly-2020-03-17-094857

Comment 5 errata-xmlrpc 2020-07-13 17:19:39 UTC

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