Hide Forgot
Description of problem: Pod deployed by CCM-operator has image set to quay.io/openshift/origin-openstack-cloud-controller-manager. This is wrong as it should use whatever is provided by the release image and it's clearly not this: docker run -it dulek/origin-release:4.10 image openstack-cloud-controller-manager quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1e50a6d96e223be64dd7c3fbb49096aff06c20d0c3fdc6a2ecc4e47edd555cf2 Version-Release number of selected component (if applicable): I tested this on 4.10 nightly How reproducible: Always Steps to Reproduce: 1. Deploy on OpenStack with CCM feature gate enabled. 2. Check images of the pods in openshift-cloud-controller-manager. Actual results: They point to quay.io/openshift/origin-openstack-cloud-controller-manager. Expected results: They should point to something like quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:<SHA> Additional info:
Verified clusterversion: 4.10.0-0.nightly-2021-11-29-191648 Deploy on OpenStack with CCM feature gate enabled.Check images of the pods: image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ea3044581f880b9d28580a651a4add538e517abe74e4f109283f96bd49870721 imagePullPolicy: IfNotPresent name: cloud-controller-manager
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.10.3 security 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:0056