Description of problem: After install openshift cluster on ibm, found that volumeBindingMode is Immediate in storageclass Version-Release number of selected component (if applicable): How reproducible: 4.10.0-0.nightly-2021-12-18-034942 Steps to Reproduce: 1.Install Openshift cluster 2.oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE ibmc-vpc-block-10iops-tier (default) vpc.block.csi.ibm.io Delete Immediate false 4h5m ibmc-vpc-block-5iops-tier vpc.block.csi.ibm.io Delete Immediate false 4h5m ibmc-vpc-block-custom vpc.block.csi.ibm.io Delete Immediate false 4h5m 3. Actual results: volumeBindingMode is Immediate in storageclass Expected results: volumeBindingMode is better to update to WaitForFirstConsumer Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Moving to MODIFIED, the fix was included in this PR: https://github.com/openshift/ibm-vpc-block-csi-driver-operator/pull/11 Specifically in this commit: https://github.com/openshift/ibm-vpc-block-csi-driver-operator/pull/11/commits/7059910af7ef1fad70ef2c1bac7516a100eeca2c
oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE ibmc-vpc-block-10iops-tier (default) vpc.block.csi.ibm.io Delete WaitForFirstConsumer false 65m ibmc-vpc-block-5iops-tier vpc.block.csi.ibm.io Delete WaitForFirstConsumer false 65m ibmc-vpc-block-custom vpc.block.csi.ibm.io Delete WaitForFirstConsumer false 65m Passed with 4.10.0-0.nightly-2021-12-23-153012
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