Bug 1795671

Summary:	Nightly upgrade tuned pods couldn't be started
Product:	OpenShift Container Platform	Reporter:	Sebastian Jug <sejug>
Component:	Node Tuning Operator	Assignee:	Sebastian Jug <sejug>
Status:	CLOSED ERRATA	QA Contact:	Simon <skordas>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	sejug
Target Milestone:	---
Target Release:	4.2.z
Hardware:	x86_64
OS:	Linux
Whiteboard:	4.2.19
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-26 07:21:27 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:	1795665
Bug Blocks:	1791916

Description Sebastian Jug 2020-01-28 15:39:37 UTC

Description of problem:
A race condition exists in upgrades for node tuning operator


How reproducible:
Rare


Steps to Reproduce:
1. Upgrade OCP version
2. ???


Actual results:
Occasionally the tuned pods would have issues starting due to a race condition around the Service Account


Expected results:
Tuned should update along with the rest of the cluster operator and components

Comment 5 Simon 2020-03-16 14:24:20 UTC

Retest positive.
Upgrade 4.2.0-0.nightly-2020-03-09-194140 -> 4.2.0-0.nightly-2020-03-16-055952

Comment 7 errata-xmlrpc 2020-03-26 07:21:27 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:0826

Comment 8 Red Hat Bugzilla 2023-09-14 05:50:52 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days