-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
False
-
-
False
-
CLOSED
-
---
-
---
-
High
-
None
Description of problem:
The template rhel8-small, datasource is having PVC in storage class ocs-external-storagecluster-ceph-rbd.
~~~
oc get pvc rhel8 -o yaml -n openshift-virtualization-os-images |yq -y '.spec'
accessModes:
- ReadWriteMany
resources:
requests:
storage: '21474836480'
storageClassName: ocs-external-storagecluster-ceph-rbd
volumeMode: Block
~~~
However, while creating the VM using UI with customize option, by default storage class is set to the one which is first matched in alphabetical order instead of the template boot source storage class. Here it is nfs-client SC. Refer attached screenshot. The SC available in this environment is below:
~~~
oc get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
nfs-client k8s-sigs.io/nfs-subdir-external-provisioner Delete Immediate false 29h
ocs-external-storagecluster-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate true 32d
ocs-external-storagecluster-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 32d
openshift-storage.noobaa.io openshift-storage.noobaa.io/obc Delete Immediate false 32d
~~~
If there is a default storage class, the default storage class is selected by default instead of the template source storage class.
Version-Release number of selected component (if applicable):
OpenShift Virtualization 4.10.4
How reproducible:
100%
Steps to Reproduce:
Refer above.
Actual results:
Customizing VM creation via template sets storageclass configuration to default
Expected results:
Like quick creation from the template, the template source storage class should be selected by default while using the customization option while creating the VM.
Additional info:
- is blocked by
-
CNV-20520 [2118967] What storageClass should the VM use if the default storageClass is different from the dataSource
- Closed
- external trackers