Description of problem: Pod deployed by CCM-operator has image set to quay.io/openshift/origin-alibaba-cloud-controller-manager. This is wrong as it should use whatever is provided by the release image. Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2022-01-28-125342 How reproducible: Always Steps to Reproduce: 1. Deploy on alibaba cluster. 2. Check images of the pods in openshift-cloud-controller-manager. Actual results: They point to quay.io/openshift/origin-alibaba-cloud-controller-manager $ oc adm release info --pullspecs registry.ci.openshift.org/ocp/release:4.10.0-0.nightly-2022-01-28-125342 Release Metadata: Version: 4.10.0-0.nightly-2022-01-28-125342 Images: NAME PULL SPEC alibaba-cloud-csi-driver quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:35349dd89ae919cb192b148c67abe2a3ea74aaae84173c5ffdba9ab5adfc81e9 alibaba-disk-csi-driver-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:260307840d56627884551a249857a831618e93e81df0578e1cbe6bcf63b4b6ef alibaba-machine-controllers quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:e2549a610a54f1c47571feb40e0139724c12261998c4a6238f5dc06514954207 aws-cloud-controller-manager quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:defbfae5465a076cf299a2589b6f059018d9605c7c74af33e8ce95d2e62aea48 Expected results: They should point to something like quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:<SHA> Additional info:
still seeing images from origin-*
checked on 4.11.0-0.nightly-2022-02-01-111605
The nightly on which this was tested didn't include the change for some reason, on the newer nightly 4.11.0-0.nightly-2022-02-01-162532 the change has worked I believe
Thanks Joel , checked on latest build available for 4.11 [miyadav@miyadav ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-02-02-012450 True False 7m21s Cluster version is 4.11.0-0.nightly-2022-02-02-012450 Steps : 1.Deploy alicloud cluster 2.[miyadav@miyadav ~]$ oc get pods oc get NAME READY STATUS RESTARTS AGE alibaba-cloud-controller-manager-57f65b8467-6p28c 1/1 Running 0 25m alibaba-cloud-controller-manager-57f65b8467-pvstr 1/1 Running 0 25m [miyadav@miyadav ~]$ oc get pod alibaba-cloud-controller-manager-57f65b8467-6p28c -o yaml | less . . . . containerStatuses: - containerID: cri-o://7e821b482c2e1b89a7896867b83ee815ce7b7aecd820c5a1b4a29827cbeca4bd image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:173888d136631d91a247c994652194d7d47dc2e3254d40ce8ab218f6d02d9125 imageID: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:173888d136631d91a247c994652194d7d47dc2e3254d40ce8ab218f6d02d9125 lastState: {} name: cloud-controller-manager ready: true restartCount: 0 started: true state: Results are as expected , moving to VERIFIED
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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069