Bug 1795665 - Nightly upgrade tuned pods couldn't be started
Summary: Nightly upgrade tuned pods couldn't be started
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Tuning Operator
Version: 4.3.z
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 4.3.z
Assignee: Sebastian Jug
QA Contact: Simon
Whiteboard: 4.3.2
Depends On: 1805033
Blocks: 1791916 1795671
TreeView+ depends on / blocked
Reported: 2020-01-28 15:25 UTC by Sebastian Jug
Modified: 2020-03-24 14:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-03-24 14:32:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-node-tuning-operator pull 108 0 None closed Bug 1795665: Do not set owner references on tuned ServiceAccount 2020-06-08 12:42:10 UTC
Red Hat Product Errata RHBA-2020:0858 0 None None None 2020-03-24 14:33:02 UTC

Description Sebastian Jug 2020-01-28 15:25:17 UTC
Description of problem:
A race condition exists in upgrades for node tuning operator

How reproducible:

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 3 Simon 2020-03-09 19:19:29 UTC
Retest positive:

4.3.0-0.nightly-2020-03-03-052929 -> 4.3.0-0.nightly-2020-03-06-102925

Comment 5 errata-xmlrpc 2020-03-24 14:32:35 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.


Note You need to log in before you can comment on or make changes to this bug.