We should check what version of CSI drivers we ship in 4.9 and possibly update them to the latest upstream release. These drivers will be considered: aws-ebs-csi-driver aws-efs-csi-driver gcp-pd-csi-driver cloud-provider-openstack (cinder, manila) csi-driver-nfs ovirt-csi-driver vmware-vsphere-csi-driver azure-disk-csi-driver
Updating aws-ebs-csi-driver in https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/1026 (to get XFS fixes).
Sorry, this is the right aws-ebs-csi-driver update: https://github.com/openshift/aws-ebs-csi-driver/pull/190
gcp-pd-csi-driver update: https://github.com/openshift/gcp-pd-csi-driver/pull/16
AzureDisk has released v1.5.1 and we have 1.5.0 in OCP 4.9. I am updating it to v1.5.1, because there is only one change and that change fixes an issue on Azure Stack Hub: https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/964
aws-efs-csi-driver: we have 1.3.1 in OCP 4.9 and upstream has 1.3.3. The only differences are in helm charts and YAML files. We do not need to update to 1.3.3 in 4.9
Verified pass.
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.9.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-2021:3759