Closed jangel97 closed 10 months ago
The problem is that your storage profile is incomplete DataVolume.storage spec is missing accessMode and no storageClass to choose profile
which usually happens when we have no pre-built storage profile. Since you are using Open Shift, if you run oc get storageprofile
you should get a list of storage profile. The name will match the storage class you are using. You have to edit the storage profile and give it appropriate accessMode and volumeMode for your particular storage. Documentation can be found here https://github.com/kubevirt/containerized-data-importer/blob/main/doc/storageprofile.md or https://docs.openshift.com/container-platform/4.13/virt/virtual_machines/virtual_disks/virt-creating-data-volumes.html#virt-customizing-storage-profile_virt-creating-data-volumes
Hey @awels thank you for your comment!
It is a bit strange because in my StorageProfile I can see this:
apiVersion: cdi.kubevirt.io/v1beta1
kind: StorageProfile
metadata:
creationTimestamp: "2023-02-13T12:30:16Z"
generation: 2
labels:
app: containerized-data-importer
app.kubernetes.io/component: storage
app.kubernetes.io/managed-by: cdi-controller
app.kubernetes.io/part-of: hyperconverged-cluster
app.kubernetes.io/version: 4.12.0
cdi.kubevirt.io: ""
name: netapp-storage-iscsi
ownerReferences:
- apiVersion: cdi.kubevirt.io/v1beta1
blockOwnerDeletion: true
controller: true
kind: CDI
name: cdi-kubevirt-hyperconverged
uid: 325181a5-06ec-43d3-ad0b-5ae53e793d76
resourceVersion: "950783059"
uid: cf02aaa9-2f86-4f03-a584-c5355bbf7f36
spec:
claimPropertySets:
- accessModes:
- ReadWriteOnce
volumeMode: Block
status:
claimPropertySets:
- accessModes:
- ReadWriteOnce
volumeMode: Block
provisioner: csi.trident.netapp.io
storageClass: netapp-storage-iscsi
And this is my storageclass netapp-storage-iscsi
:
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
creationTimestamp: "2023-02-13T12:30:16Z"
name: netapp-storage-iscsi
resourceVersion: "658168888"
uid: fa74ed85-3cd7-49c4-84f8-718c2ae09c05
parameters:
backendType: ontap-san
fsType: ext4
selector: classification=restricted
provisioner: csi.trident.netapp.io
reclaimPolicy: Delete
volumeBindingMode: Immediate
So, according to the docs everything should be set right?
Kind regards,
Can you make that storage class the default storage class? Or specify the storage class in the datavolume storage section.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
I am trying to create a template from openshift 4.13
This is how my template looks:
Right after creating my template, I try to create a new VM from the catalog. The VM looks like stopped and when I describe the DV I see the following error:
I can see a PVC is created but it has incomplete information:
Am I doing something wrong in the template? Is there anything I am missing? The expected behaviour would be that right after creating the VM a DV poinitng to containerdisk
docker://images.paas/jmorenas/rhel9
should start downloading the containerdisk.Thanks in advance,