Bug 1983424
| Summary: | [cnv 2.6.6] vm-import-controller pod CrashLoops indefinitely because of wrong API version for VirtualMachine | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Oren Cohen <ocohen> |
| Component: | V2V | Assignee: | Fabien Dupont <fdupont> |
| Status: | CLOSED DUPLICATE | QA Contact: | Daniel Gur <dagur> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.6.6 | CC: | amastbau, cnv-qe-bugs, ibesso, stirabos |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-19 11:48:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 1982760 *** |
Description of problem: Upon Installation of CNV 2.6.6-43, or upgrade to that version, all pods are Running and Ready, except the vm-import-controller pod, which is failing and restarted in a loop. Here is the relevant log of the pod: {"level":"error","ts":1626611871.6030169,"logger":"controller-runtime.source","msg":"if kind is a CRD, it should be installed before calling Start","kind":"VirtualMachine.kubevirt.io","error":"no matches for kind \"VirtualMachine\" in version \"kubevirt.io/v1\"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/remote-source/app/vendor/github.com/go-logr/zapr/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:117\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:140\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:175\nsigs.k8s.io/controller-runtime/pkg/manager.(*controllerManager).startRunnable.func1\n\t/remote-source/app/vendor/sigs.k8s.io/contro... {"level":"error","ts":1626611871.603378,"logger":"cmd","msg":"Manager exited non-zero","error":"no matches for kind \"VirtualMachine\" in version \"kubevirt.io/v1\"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/remote-source/app/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/remote-source/app/cmd/manager/main.go:159\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:204"} Version-Release number of selected component (if applicable): CNV Bundle v2.6.6-43 vm-import-controller v2.6.6-3 IIB index image: registry-proxy.engineering.redhat.com/rh-osbs/iib:91026 Brew build info: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1663446 How reproducible: 100% Steps to Reproduce: 1. Deploy CNV of the mentioned version, or upgrade to it from a previous version (e.g. 2.6.5). 2. 3. Actual results: virt-import-controller pod crashes because it watches the wrong API version of the resource "VirtualMachine". It looks for kubevirt.io/v1, while in 2.6, it is actually kubevirt.io/v1alpha3 Expected results: This pod is not crashing, and the installation of CNV completed successfully. Additional info: Note: You will not be able to reproduce this bug if CRDs from CNV 4.8 are deployed in the cluster beforehand. You should deploy it on a fresh cluster without any CRDs of kubevirt.io.