Bug 1724274

Summary: During upgrade, node-tuning operator status rapidly alternates between new and old version
Product: OpenShift Container Platform Reporter: Mike Fiedler <mifiedle>
Component: Node Tuning OperatorAssignee: Jiří Mencák <jmencak>
Status: CLOSED ERRATA QA Contact: Simon <skordas>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: ccoleman, jmencak, sejug, skordas
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1719967 Environment:
Last Closed: 2019-10-16 06:32:41 UTC Type: ---
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: 1719967, 1729273    
Bug Blocks:    

Comment 1 Mike Fiedler 2019-06-26 16:02:10 UTC
Clone for 4.2.

PR is https://github.com/openshift/cluster-node-tuning-operator/pull/67

Comment 3 Simon 2019-06-27 19:56:02 UTC
I've upgrade and downgrade few times between 4.2.0-0.nightly-2019-06-26-043058 and 4.2.0-0.nightly-2019-06-27-041730 (before fix and after fix) and also between 4.2.0-0.nightly-2019-06-27-041730 and 4.2.0-0.nightly-2019-06-27-081948 (both versions after fix)
With the newest one I'm not able to reproduce the issue. :)

Comment 4 errata-xmlrpc 2019-10-16 06:32:41 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-2019:2922