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. This blocks forming a nightly. 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.
cluster-node-tuning-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe0c1375006889511559149cf54434d399340bbc6068119d772bc8295262ae0f io.openshift.build.commit.url=https://github.com/openshift/cluster-node-tuning-operator/commit/8654d1c9558d0d5ef03d14373c877ebc737f9736 url=https://access.redhat.com/containers/#/registry.access.redhat.com/openshift/ose-cluster-node-tuning-operator/images/v4.7.0-202010140812.p0 No cluster-node-tuned images. Clusterversion: 4.7.0-0.nightly-2020-10-15-051208
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633