Bug 1956268
| Summary: | Web console displays a "Running cutover" migration plan status before the cutover time set in the Migration custom resource | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Amos Mastbaum <amastbau> | ||||
| Component: | User Experience | Assignee: | Mike Turley <mturley> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ilanit Stein <istein> | ||||
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> | ||||
| Priority: | high | ||||||
| Version: | 2.0.0 | CC: | apinnick, fdupont, istein, mguetta | ||||
| 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:47 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: |
|
||||||
A user setting the cutover time through the UI wouldn't have this problem. Targeting MTV 2.1.0. Opened a fix: https://github.com/konveyor/forklift-ui/pull/573 This PR should fix the issue, but @amastbau I'm confused about one detail of your report. In reproducing the bug, I set a cutover time on a plan that was running precopies (the pipeline steps had not yet started). It didn't result in showing "Running cutover", instead it showed "Preparing for cutover" because it shows that until it sees a start time on the first pipeline step. Can you reproduce it again and post the `status` part of the plan object, both before and after you set the cutover on the migration? I don't think the pipeline steps should have start times until the cutover time is reached, and that may indicate a bug in the controller. It's my understanding that the pipeline status is only used during cutover. Retargeting for 2.0.0 at Fabien's request. Backport PR here: https://github.com/konveyor/forklift-ui/pull/576 The fix is in build 2.0.0-8 / iib:72981. @mturley The original Scenario was setting the cut-over date to the far future with the migration CR Creation. I verified the following scenarios: 1.Add a future time with CR Creation 2.Add a future time with CR Creation and then change to pass date 3.Set Cut-over date to the future after the CR is created 4.Set Cut-over date to the past after the CR is created 5.Change the cut-over date before/after the 1st pre-copy In all cases the UI indicated the expected phase. build 2.0.0-8 / iib:72981. build 2.0.0-8 / iib:72981 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 |
Created attachment 1778910 [details] UIVSAPI Description of problem: If setting any cut-over date-time to the migration CR, the UI indicates Plan Status: Running Cut-over. The Cut-over time may still be a few phases a head,. it has not really started yet. Version-Release number of selected component (if applicable): How reproducible: Migrate using CLI setting a future cutover date in the migration CR. Steps to Reproduce: 1. 2. 3. Actual results: The UI indicates Plan Status: Running Cut-over (see attached) Expected results: The status in the UI should indicate to correct plan phase. Additional info: