Bug 1887089

Summary:	cluster-node-tuning-operator refers to missing cluster-node-tuned image
Product:	OpenShift Container Platform	Reporter:	Luke Meyer <lmeyer>
Component:	Node Tuning Operator	Assignee:	Jiří Mencák <jmencak>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Fiedler <mifiedle>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	sejug
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-11 20:49:30 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:	1887088
Bug Blocks:

Description Luke Meyer 2020-10-10 18:10:37 UTC

This bug was initially created as a copy of Bug #1887088

I am copying this bug to backport to 4.6

Description of problem:
Per https://issues.redhat.com/browse/ART-2044 the tuned container is obsolete. However it is still referred to in cluster-node-tuning-operator (and thus the CVO) as cluster-node-tuned. 

Actual results:
https://amd64.ocp.releases.ci.openshift.org/releasestream/4.7.0-0.nightly/release/4.7.0-0.nightly-2020-10-10-172258 shows
> error: unable to create a release: operator "cluster-node-tuning-operator" contained an invalid image-references file: no input image tag named "cluster-node-tuned"

Expected results:
no reference to "cluster-node-tuned" tag

Additional info:
4.6 has a similar reference. It is currently fulfilled by a two-month-old tag. I'll clone this bug for that, but as long as it's not actually in use by anything, it may not require removal from the nightly for GA, although that would be ideal. 

It doesn't look like any manifest has referred to this image since 4.3, so you may want to backport the change through 4.4.