Bug 1941321 - [v2v] [VMIO] [API] Warm Migration Should not fail when setting Past Cut-Off Date
Summary: [v2v] [VMIO] [API] Warm Migration Should not fail when setting Past Cut-Off Date
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.6.2
Assignee: Sam Lucidi
QA Contact: Amos Mastbaum
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-21 15:45 UTC by Amos Mastbaum
Modified: 2021-05-04 20:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-04 20:09:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:1502 0 None None None 2021-05-04 20:09:23 UTC

Description Amos Mastbaum 2021-03-21 15:45:10 UTC
Description of problem:

If Setting any past date in vmimport CR (spec.finalizeDate; at creation time),

The VMImport Status indication the flow is CreatingTargetVM: Creating virtual machine.

For the Controller's  Logs:
--------------------------
2021-03-21T15:24:32.735694897Z {"level":"error","ts":1616340272.7355661,"logger":"controller","msg":"Reconciler error","controller":"virtualmachineimport-controller","name":"v2v-3disks-b","namespace":"amos","error":****"DataVolume.cdi.kubevirt.io \"e7e7fd9b-30e4-4a66-aac0-41e42ca0a1bc-2000\" not found"****,"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/internal/controller.(*Controller).reconcileHandler\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:237\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:209\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:188\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90"}
 



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. vmimport a vm using warm migration setting past cut-off time (spec.warm=true; spec.finalizeDate=)
2.
3.

Actual results:
The Import remains at CreatingTargetVM: Creating virtual machine


Expected results:
The last phase of the import should start after the 1st snapshot(s) is/are done.


Additional info:

Comment 2 Ilanit Stein 2021-04-11 13:19:28 UTC
@Fabien,

Can this bug be targeted to 2.6.2 please?

Thanks,
Ilanit.

Comment 3 Fabien Dupont 2021-04-16 07:21:48 UTC
The fix should be part of hco-bundle-registry build v2.6.2-4 / iib:66925.

Comment 4 Amos Mastbaum 2021-04-25 09:04:17 UTC
Verified 2.6.2.
import started in cold migration (no snapshot taken- verified in vmware)

Comment 10 errata-xmlrpc 2021-05-04 20:09:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Virtualization 2.6.2 Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1502


Note You need to log in before you can comment on or make changes to this bug.