Bug 1956467
| Summary: | If a successfully migrated source VM is deleted, a new migration plan with different VMs fails because the scheduler is looking for the deleted VM | ||
|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | David Vaanunu <dvaanunu> |
| Component: | General | Assignee: | Sam Lucidi <slucidi> |
| Status: | CLOSED ERRATA | QA Contact: | David Vaanunu <dvaanunu> |
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | high | ||
| Version: | 2.0.0 | CC: | apinnick, fdupont, istein, 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: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: | |||
|
Description
David Vaanunu
2021-05-03 18:25:11 UTC
What are the VMs in the second plan? The same as the first plan? I fail to understand what you are trying to do here. The second plan use diff VMs I got a similar behavior when I created a plan from CLI, and run it from CLI, and then I deleted the plan from UI. The migration CR was not deleted. and when I tried to run the plan again, it didn't start as described here in the bug. Maybe in your flow the previous migration CR was not deleted? There is a bug that when a plan CR is deleted in CLI the migration CR should be deleted too. But I think that even if we run a plan, though it's previous CR still exist, it should not cause the plan to be at a "non starting" state, but rather fail. @Fabien, wdyt? Would it be possible to have access to an environment where it's happening? I still don't understand the exact flow. @slucidi, could you please help troubleshooting this? The issue here is a specific edge case in the scheduler when it encounters a completed Plan, but one or more of the source VMs on that Plan have been removed from the inventory. VMs on completed Plans can't affect the schedule because they're not running, but they shouldn't be considered by the scheduler at all. The scheduler needs to A) disregard completed Plans, and B) not fail if a VM can't be found in the inventory. This is unrelated to any issues regarding Migration CRs being left behind after a plan is deleted. The fix is in build 2.0.0-10 / iib:73160. The second plan use diff VMs Verified on MTV_2.0.0-12 / iib:73572 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 |