Description of problem:
Need a more clear event message for ebs.csi.aws.com provisioner
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install an OCP4.6 cluster on AWS
2. Clone a storage class with ebs.csi.aws.com provisioner and Immediate bind mode.
3. Create a PVC with "RWX" or "ROX" access modes
PVC is in pending status and gets the following event:
Warning ProvisioningFailed <invalid> (x6 over <invalid>) ebs.csi.aws.com_ip-10-0-49-238.us-east-2.compute.internal_003d900a-1a4e-43e0-ae5e-3da6bbe2c24d failed to provision volume with StorageClass "gp2-csi-i": rpc error: code = InvalidArgument desc = Volume capabilities not supported
The event for internel provisioner "kubernetes.io/aws-ebs" is:
Warning ProvisioningFailed <invalid> persistentvolume-controller Failed to provision volume with StorageClass "gp2-i": invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce] are supported
The event for internal provisioner is more clear.
Node Log (of failed PODs):
StorageClass Dump (if StorageClass used by PV/PVC):
I've submitted  to address this issue upstream. Once it's merged we can backport it into our driver.
Verified with: 4.6.0-0.nightly-2020-09-26-202331
failed to provision volume with StorageClass "gp2-csi": rpc error: code = InvalidArgument desc = Volume capabilities MULTI_NODE_MULTI_WRITER not supported. Only AccessModes[ReadWriteOnce] supported.
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.