When creating VM from console, select the option to customize VM creation. Select the disks and edit the disk to select the storage class. The 'AccessMode' and 'VolumeMode' are listed for the selected storage class and those are static values and do not change according to the selected storage class.

We have an issue where selecting the volumemode which is not supported by storage class, then DV creation happens forever (https://issues.redhat.com/browse/CNV-55147).

So to avoid customers ending up in this scenario, the validation should be added in the product. At the same time, it would be very helpful if the volumemode is refreshed according to the selected storage class.
If this is not possible, then at least an 'info/caution note' to be added to the users to select the volumemode as supported by storage class.

CNV v4.18

Always

1.Create VM from template, and select customize VM
2. Edit the disk, select rootdisk, select the storage class which doesn't support volumeMode 'Block' for example: trident-nfs
3. Now the volume mode stays with default value as 'Block'
4. Create VM

VM creation doesn't complete.

1. The volumeMode should get updated to 'Filesystem' only value when the storage profile supports only 'Filesystem'
2. If the above is not possible, add a important/caution note to users to select the volumeMode as supported by storage class