ok.. known issue: https://github.com/harvester/harvester/issues/7875 - i thought we added an ui option for it

not in

1.5.0_rc3

. And I am getting stuck on the image creation part.

dang

want me to create an issue?

i'll add to the existing one to make sure it retains the priority

tell them “Brian Durden” needs it. 😄

thanks for bringing this up

thanks for helping!

Hi @thousands-advantage-10804, Sorry, I missed this topic. The Harvester VM Image did not have the volumeMode concept. The case you encounter might related to the StorageProfile (this concept comes from the CDI). I saw the some

Portworx

provisioner here. (https://github.com/kubevirt/containerized-data-importer/blob/main/pkg/storagecapabilities/storagecapabilities.go#L94-L101) What is your provisioner? And what is the corresponding storageprofile? You can define your target volumeMode/accessMode on the storageprofile. (This means if you only want the corresponding StorageClass to create the

volumeMode: Block

, you can manually update the StorageProfile) For the original design, the VM Image did not include any volume related concept. So, we might not make much change at this moment (but you can achieve this by changing the storage file). We might redesign the UX experience after v1.5.0, so that might be a good topic for us to improve on. Could you update the StorageProfile and use it?

I tried to update the storageprofile. It instantly flips back. There are 2 paths here.

hmm, how did you update the profile?

What is your updated content about the spec section?

I was being dumb.. I got it updated…

Nice! I am happy to see it updated 😄

https://docs.portworx.com/portworx-csi/release-notes.html#known-issues for the win