Bug 2048478

Summary: [alicloud] CCM deploys alibaba-cloud-controller-manager from quay.io/openshift/origin-*
Product: OpenShift Container Platform Reporter: Joel Speed <jspeed>
Component: Cloud ComputeAssignee: Joel Speed <jspeed>
Cloud Compute sub component: Cloud Controller Manager QA Contact: sunzhaohua <zhsun>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: aarapov, aos-bugs, zhsun
Version: 4.10   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2047998 Environment:
Last Closed: 2022-03-10 16:42:51 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: 2047998    
Bug Blocks:    

Description Joel Speed 2022-01-31 10:40:09 UTC 
+++ This bug was initially created as a clone of Bug #2047998 +++

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:
Comment 4 sunzhaohua 2022-02-07 07:13:26 UTC 
Verified
clusterversion: 4.10.0-0.nightly-2022-02-06-233933

$ oc adm release info --pullspecs registry.ci.openshift.org/ocp/release:4.10.0-0.nightly-2022-02-06-233933

Pull From: registry.ci.openshift.org/ocp/release@sha256:77fb6503314186c48980d60bf21283b57ca5e48b0a814b1390853157903c7a7a

Release Metadata:
  Version:  4.10.0-0.nightly-2022-02-06-233933

Images:
  NAME                                           PULL SPEC
  alibaba-cloud-controller-manager               quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4e1ffd445ab56d097eca9d850ed2deb4b0e8ea9c671a994a1009ea2a7220fdac
  alibaba-cloud-csi-driver                       quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:bdb5b86d3659f5468e98813ee12e060197d422e9b28ecb8b2dbe5f6d525b5c9c
  alibaba-disk-csi-driver-operator               quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:de2a7e46f99ea8a7d948484a2ad767ddb9a44f67e00957f6f53a11b4e4a15c16
Comment 6 errata-xmlrpc 2022-03-10 16:42:51 UTC 
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