Bug 1723569 - Need to clean up extraneous secrets in node tuning operator namespace
Summary: Need to clean up extraneous secrets in node tuning operator namespace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Tuning Operator
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Jiří Mencák
QA Contact: Simon
URL:
Whiteboard:
: 1734606 (view as bug list)
Depends On: 1718842
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-24 20:21 UTC by Jiří Mencák
Modified: 2019-10-17 12:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1718842
Environment:
Last Closed: 2019-10-16 06:32:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:32 UTC

Comment 4 Mike Fiedler 2019-06-25 12:50:53 UTC 
This bz tracks the issue for 4.2.   The correct PR is https://github.com/openshift/cluster-node-tuning-operator/pull/63 which is merged and should be included in the newest 4.2 nightly builds.   Moving this to ON_QA.
Comment 5 Simon 2019-06-25 19:44:07 UTC 
Verification: POSITIVE
Started with quay.io/openshift-release-dev/ocp-release:4.1.0

Node tuning operator created extraneous secrets.

After upgrading to upstream:

oc get clusteroperator node-tuning
NAME          VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
node-tuning   4.2.0-0.nightly-2019-06-25-163533   True        False         False      2m9s


All extraneous secrets were deleted and no new extraneous secrets were created.
Comment 6 Devan Goodwin 2019-08-02 15:02:02 UTC 
*** Bug 1734606 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2019-10-16 06:32:20 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
Note You need to log in before you can comment on or make changes to this bug.