search

kubevirt / vm-import-operator

Operator for importing VMs from RHV to KubeVirt
Apache License 2.0
16 stars 23 forks source link

DataVolume.cdi.kubevirt.io error: no matches for kind "DataVolume" #522

Closed webnotesweb closed 8 months ago

webnotesweb commented 1 year ago

Deployment of vm-import-operator keeps failing with this error:

{"level":"error","ts":1695820108.586178,"logger":"controller-runtime.source","msg":"if kind is a CRD, it should be installed before calling Start","kind":"DataVolume.cdi.kubevirt.io","error":"no matches for kind \"DataVolume\" in version \"cdi.kubevirt.io/v1alpha1\"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/opt/app-root/src/vm-import-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start\n\t/opt/app-root/src/vm-import-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:117\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/opt/app-root/src/vm-import-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:140\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start\n\t/opt/app-root/src/vm-import-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:175\nsigs.k8s.io/controller-runtime/pkg/manager.(*controllerManager).startRunnable.func1\n\t/opt/app-root/src/vm-import-operator/vendor/sigs.k8s.io/controller-runtime/pkg/manager/internal.go:661"}

K8s version: v1.27.6 KubeVirt v1.0.0 CDI: v1.57.0 VMIO: v0.4.0

StorageClass is local-path (rancher.io/local-path)

Only related info that I was able to find is here https://github.com/kubevirt/kubevirt/issues/7078#issuecomment-1022330007

Any insight/ideas/help would be highly appreciated.

I am able to create VMs and access them, for example this works just fine.

kubevirt-bot commented 9 months ago

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

kubevirt-bot commented 8 months ago

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