Description of problem: The azure-file-csi-driver and azure-file-csi-driver-operator don't use the downstream images: image: quay.io/openshift/origin-azure-file-csi-driver:latest image: quay.io/openshift/origin-azure-file-csi-driver-operator:latest Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2021-11-28-164900 How reproducible: Always Steps to Reproduce: 1. Create azure cluster 2. Install Azure-file CSI Driver with enable the feature gate 3. Check images used by Azure-file CSI Driver related pod image: quay.io/openshift/origin-azure-file-csi-driver:latest image: quay.io/openshift/origin-azure-file-csi-driver-operator:latest Actual results: The azure-file-csi-driver and azure-file-csi-driver-operator don't use the downstream images Expected results: The azure-file-csi-driver and azure-file-csi-driver-operator should use the downstream images Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Verified pass on 4.10.0-0.nightly-2021-12-03-213835
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