OpenShift Virtualization: Failed to create VM on OpenShift Virtualization UI if no default StorageClass exists in OCP cluster
Summary: The VM cannot be created via OpenShift Virtualization if no default StorageClass exists in OCP cluster. Because non-default StorageClass cannot be selected for rootdisk or for the user added disks. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Failed to create new VM via OpenShift Virtualization UI if no default StorageClass exists in OCP cluster.
Cause
It is an issue of OpenShift Virtualization feature.
For the VM rootdisk and user added disks, they can only select the default StorageClass in the OCP cluster.
Non-default StorageClass cannot be selected.
For the VM rootdisk and user added disks, they can only select the default StorageClass in the OCP cluster.
Non-default StorageClass cannot be selected.
Resolution
There are two options to workaround this issue:
Example of a default StorageClass:
- Create a default StorageClass with the annotation "storageclass.kubernetes.io/is-default-class: 'true'".
- Modify the existing StorageClass mcp-pf-fs-storageclass, set it to default StorageClass
Example of a default StorageClass:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: my-sc-1
annotations:
storageclass.kubernetes.io/is-default-class: 'true'
provisioner: csi-vxflexos.dellemc.com
parameters:
csi.storage.k8s.io/fstype: ext4
storagepool: SP-SW_NVME-1
systemID: efc2f2902330a60f
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumerAffected Products
APEX Cloud Platform for Red Hat OpenShiftArticle Properties
Article Number: 000217665
Article Type: Solution
Last Modified: 20 فبراير 2026
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.