Bug 1986839 - Warm migration plan displays "Running cutover" status at start
Summary: Warm migration plan displays "Running cutover" status at start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: User Experience
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.1.0
Assignee: Mike Turley
QA Contact: Maayan Hadasi
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-28 12:42 UTC by Maayan Hadasi
Modified: 2021-08-26 07:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-26 07:09:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (48.05 KB, image/png)
2021-07-28 12:42 UTC, Maayan Hadasi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github konveyor forklift-ui pull 736 0 None None None 2021-08-04 14:25:15 UTC
Github konveyor forklift-ui pull 737 0 None None None 2021-08-04 14:26:03 UTC
Red Hat Product Errata RHEA-2021:3278 0 None None None 2021-08-26 07:09:32 UTC

Description Maayan Hadasi 2021-07-28 12:42:02 UTC 
Created attachment 1806712 [details]
screenshot

Description of problem:
"Running cutover" displayed in 'Migration plans' page, once warm migration is started
After few seconds UI shows "Running - performing incremental data copies"


Version-Release number of selected component (if applicable):
mtv-operator-bundle-container-2.1.0-34
(baremetal)


How reproducible:
100%


Attachment:
screenshot
Comment 1 Fabien Dupont 2021-08-04 13:48:57 UTC 
@mguetta could you please provide a reproducing environment to Mike Turley?
Comment 2 Mike Turley 2021-08-04 14:33:17 UTC 
I think I found the issue, but I can't be sure without testing in a real environment. This PR should be harmless though if we just want to merge and verify in QE.
https://github.com/konveyor/forklift-ui/pull/736 (backport: https://github.com/konveyor/forklift-ui/pull/737)

If I'm correct, the issue comes down to a transient state where a warm plan has the Executing condition and does have data in its `status` property, but does not yet have data in any of its `status.migration.vms[].warm.precopies` arrays. So it doesn't fit the cases for 'StartingCutover' or 'Copying', and since the plan has the Executing condition the UI falls back to the 'PipelineRunning' state when none of the other state logic applies. This PR changes the fallback state to 'Starting' in this case (previously, this case was only used if there was no `status` data at all.
Comment 3 Mike Turley 2021-08-04 15:06:11 UTC 
Fix is merged. If you'd prefer to verify with the next build instead of setting up a reproducing environment for me, that would be fine. I'm pretty confident this was the root cause.
Comment 4 Maayan Hadasi 2021-08-05 06:39:27 UTC 
Hi @mturley, 

You can use baremetal cloud10 to reproduce the issue.
Sending you the cluster's details by mail
Comment 5 Fabien Dupont 2021-08-05 06:50:06 UTC 
Please verifiy with build 2.1.0-41 / IIB 96258.
Comment 6 Maayan Hadasi 2021-08-05 07:40:30 UTC 
Verified as fixed.


Versions:
mtv-operator-bundle-container-2.1.0-41
CNV 4.8.0-451 iib 86746
OCP 4.8.0-rc.1
(BareMetal)
Comment 9 errata-xmlrpc 2021-08-26 07:09:27 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 (Migration Toolkit for Virtualization 2.1.0), 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:3278
Note You need to log in before you can comment on or make changes to this bug.