+++ This bug was initially created as a clone of Bug #2058149 +++ Description of problem: For deployment cluster-network-addons-operator, MULTUS_IMAGE is pointing to brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift/ose-multus-cni:v4.1.0-7.1556622314 Version-Release number of selected component (if applicable): 4.10.0 How reproducible: 100% Steps to Reproduce: 1. Check all the container images of cnv deployments. 2. 3. Actual results: (cnv-tests) [cnv-qe-jenkins@c01-dbn1-410-vvhqw-executor cnv-tests]$ kubectl get deployment -n openshift-cnv cluster-network-addons-operator -o json |jq ".spec.template.spec.containers[0].env" [ { "name": "MULTUS_IMAGE", "value": "brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift/ose-multus-cni:v4.1.0-7.1556622314" }, Expected results: All would point to registry.redhat.io images Additional info: --- Additional comment from Petr Horáček on 2022-02-24 12:26:37 UTC --- We are not deploying Multus on D/S, but it would be safer to omit the image reference completely. Thanks for reporting this.
@stirabos thanks a lot for helping us with this one. Would it be ok to backport https://gitlab.cee.redhat.com/cpaas-midstream/openshift-virtualization/hco-bundle-registry/-/merge_requests/15/diffs to 4.10?
Verified. kubevirt-hyperconverged-operator.v4.10.2 OpenShift Virtualization 4.10.2 Multus image is not set by cnao. [cnv-qe-jenkins@n-adiz410-jvgwf-executor cnv-tests]$ oc get deployment -n openshift-cnv cluster-network-addons-operator -o json |jq ".spec.template.spec.containers[0].env" [ { "name": "MULTUS_IMAGE", "value": "NOT_AVAILABLE" }, {
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 Virtualization 4.10.2 Images security and bug fix 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-2022:5026