Description of problem: Since 3.x and 4.x use different volumeBindingMode in storageclass, We should show volumeBindingMode info in storageclas's overview page. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-08-01-113533 How reproducible: Always Steps to Reproduce: 1.Set up a 4.2 cluster on AWS or Azure. 2.Check storage class overview page. Actual results: The storage class overview does not show info about volumeBindingMode Expected results: volumeBindingMode should be there to make things clear as it has different values than OCP 3.x Additional info: In 3.x, volumeBindingMode is Immediate. In 4.1, AWS use volumeBindingMode WaitForFirstConsumer. In 4.2, AWS/GCP/Azure/Openstack use volumeBindingMode WaitForFirstConsumer, VMware vSphere use volumeBindingMode Immediate Also we will have 3.x to 4.x migration. Diff volumeBindingModes will cause diff scheduling.
PR: https://github.com/openshift/console/pull/2277
Now on Storage Class Overview page, we have 'Volume Binding Mode' field to show sc's volumeBindingMode Verified on 4.2.0-0.nightly-2019-08-10-002649
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, 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/RHBA-2019:2922