Bug 1986839
| Summary: | Warm migration plan displays "Running cutover" status at start | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Maayan Hadasi <mguetta> | ||||
| Component: | User Experience | Assignee: | Mike Turley <mturley> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Maayan Hadasi <mguetta> | ||||
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> | ||||
| Priority: | medium | ||||||
| Version: | 2.1.0 | CC: | fdupont, istein | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.1.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-08-26 07:09:27 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: | |||||||
| Attachments: |
|
||||||
@mguetta could you please provide a reproducing environment to Mike Turley? 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. 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. Hi @mturley, You can use baremetal cloud10 to reproduce the issue. Sending you the cluster's details by mail Please verifiy with build 2.1.0-41 / IIB 96258. 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) 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 |
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