StorageProfiles ease the burden of selecting the optimal PVC parameters (AccessMode and VolumeMode) for known CSI provisioners. As we encounter new provisioners we should determine the correct values and update our internal table in CDI so that our customers will get a better out of the box experience. Having a correct storage profile can also make VM provisioning order of magnitude faster (host copy vs. CSI clones). Several customer support cases have already arisen because the OCP certified provisioner had an empty or incorrect admin provided storage profile. Version-Release number of selected component (if applicable): OpenShift Virtualization 4.12.0 How reproducible: 100% Steps to Reproduce: Create DV with storage class which has no StorageProfile defaults (e.g. AWS ElasticFileSystem provisioner efs.csi.aws.com) Actual results: Empty StorgaeProfile is created Expected results: StorgaeProfile with default AccessMode and VolumeMode should be created Additional info:
verified on OpenShift Virtualization 4.13.3
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 (Important: OpenShift Virtualization 4.13.3 Images security and bug fix 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-2023:4664