Bug 1999163
| Summary: | Status of completed migration plan is "Running" on the "Migration plans" page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Michael Spaxman <mspaxman> | ||||
| Component: | User Experience | Assignee: | Michael Spaxman <mspaxman> | ||||
| Status: | CLOSED ERRATA | QA Contact: | kpunwatk | ||||
| Severity: | low | Docs Contact: | Avital Pinnick <apinnick> | ||||
| Priority: | unspecified | ||||||
| Version: | 2.1.0 | CC: | fdupont, mturley | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.2.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-12-09 19:20:56 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: |
|
||||||
Please verify with build 2.2.0-1 / iib:104622. Verified on MTV-2.2.0-80 / iib:132252, CNV-4.9.1-11. Steps to Verify: 1. Create a plan with settings that match the attached plan metadata JSON 2. Started the migration and let it complete. Noticed that the plans table shows the "Succeeded" state once it is finished successfully 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.2.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:5066 |
Created attachment 1819116 [details] Example plan metadata to reproduce issue Description of problem: Certain combination of plan metadata can cause the UI to get confused about the status of the plan, showing it in the starting state when it should show completed. Version-Release number of selected component (if applicable): 2.1.0 How reproducible: Steps to Reproduce: 1. Create a plan with settings that match the attached plan metadata JSON 2. Start the migration and let it complete. 3. Notice the plans table shows that migration in a running state. Actual results: The plans table shows the plan as running even though it has finished. Expected results: The plans table shows the finished plan in "Finished - succeeded" state once it is finished successfully. Additional info: Please see attached plan metadata for plan settings to reproduce.