Closed Smithx10 closed 3 months ago
dataVolumeTemplates:
- metadata: name: bruce spec: pvc: accessModes:
- ReadWriteOnce resources: requests: storage: 5Gi
I think the issue is here, if you want to infer from the StorageProfile you created, you need to use storage
instead of pvc
:
https://github.com/kubevirt/containerized-data-importer/blob/main/doc/storageprofile.md#handling-the-dv-with-defaults-from-storage-profiles
I think what happens is that you are using a raw block ZFS storage class, but this is a Filesystem PVC request.
Yes I think Alex is correct, if omited the volumeMode defaults to filesystem, and the source is block, and thus doing a clone will fail. By using the pvc
stanza instead of storage
CDI will use whatever you pass it and not infer anything from the storage profile. I am assuming chaning it fixed it since this is 2 weeks old. Can we close this issue?
I am going to close this issue due to inactivity. Please feel free to reopen if you'd like to continue the investigation.
I am attempting to configure "block" storage profiles with openebs/zfs-localpv to deploy a vm using a fedora block pv.
I've been trying to find documentation on how to do this, and am coming up short. Additional eyes / Help would be much appreciated.
Where I get stuck
VM Defintion
Fedora PVC
Datavolume source
Snap Class
Storage Class
Storage Profile
Kube version
Kernel
OS Release
CDI Deployment