Description of problem: ------------------------ I noticed that a plan in Critical state because of existing target VM didn't switch to Ready state after target VM was deleted Version-Release number of selected component (if applicable): ------------------------------------------------------------- MTV 2.0.0-20 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Create a plan with VMs that already exist on the target 2.Plan status shows 'Critical' Target VM already exists. 3.Delete target VMs Actual results: --------------- Plan continues to be in 'Critical' state. Expected results: ----------------- Plan should switch to 'Ready' state. Additional info: ----------------
Fixed: https://github.com/konveyor/forklift-controller/pull/232.
Please test with the mtv-operator-bundle-2.1.0-5 build / iib:85044.
Verified on MTV build 2.1.0-44 IIB 96817. 1.Create a plan with VM that already exist on the target 2.Plan status shows 'Critical' Target VM already exists. 3.Delete target VM 4.After deleting can see the migration plan in Ready state and also Plan run 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 (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