Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1953119

Summary:	Restarting a canceled warm migration plan shows incorrect status in the UI
Product:	Migration Toolkit for Virtualization	Reporter:	Nandini Chandra <nachandr>
Component:	General	Assignee:	Sam Lucidi <slucidi>
Status:	CLOSED ERRATA	QA Contact:	Nandini Chandra <nachandr>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	high
Version:	2.0.0	CC:	apinnick, fdupont, istein, jortel, mturley, slucidi
Target Milestone:	---
Target Release:	2.0.0
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-06-10 17:11:46 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:

Description Nandini Chandra 2021-04-23 23:31:17 UTC

Description of problem:
-----------------------
When a canceled warm migration is restarted, 
1)the UI shows that it is running a cutover. 
2)Clicking on the plan doesn't show the precopy view, but shows the post cutover view instead.It shows that the migration is stuck at the 'Transfer disks' step after some data is copied.
3)At this point, the OCP console shows that migration is stuck at 10% with this message -CopyingPaused: Waiting for next warm import stage. If the cutover button is pressed, both the 'Transfer disks' and 'Convert image to kubevirt' steps complete.

I'd expect the migration to progress like a regular warm migration.


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Start a warm migration.
2.Cancel the warm migration.
3.Restart the warm migration


Actual results:
---------------


Expected results:
----------------


Additional info:
---------------

Comment 1 Mike Turley 2021-04-24 00:07:24 UTC

Attaching a copy of the Plan CR after starting a migration for the first time, when it displays in the UI that is running precopies (mturley-test-2-precopying.json) and a copy of the same plan after it has been canceled and restarted (mturley-test-2-retryingprecopy.json)

Comment 4 Mike Turley 2021-04-24 00:11:17 UTC

You can observe that the second copy of the plan CR has a `status.migration.completed` property (which is not in the first copy of the plan CR, it was added when the plan was canceled) and it is present even after the second migration starts. If that property is cleared when the retry migration starts, the UI bug should be fixed.

Comment 5 Mike Turley 2021-04-26 14:34:20 UTC

This is a pretty nasty one since you can't monitor precopies on the affected plan at all. Targeting for 2.0.0 if we can manage that?

Comment 6 Sam Lucidi 2021-04-26 20:03:09 UTC

https://github.com/konveyor/forklift-controller/pull/234

Comment 7 Fabien Dupont 2021-05-03 12:10:33 UTC

The fix should be part of build mtv-operator-bundle-container-2.0.0-4 / iib:72115.

Comment 8 Nandini Chandra 2021-05-06 17:39:50 UTC

Verified on mtv-operator-bundle-container-2.0.0-4

Comment 11 errata-xmlrpc 2021-06-10 17:11:46 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 (MTV 2.0.0 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:2381