Description of problem: ---------------------- We should add a check for existing VMs on the target provider before doing a migration to the target provider and display a message in the UI if a VM already exists on the target provider. Version-Release number of selected component (if applicable): ---------------------------- How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Create a migration plan to migrate an existing VM from VMware to OCP . Actual results: --------------- The migration succeeds. Expected results: ----------------- 1)Add preflight check for existing VMs on the target provider so that migration doesn't proceed and 2)display an appropriate message in the UI to let the user know why the migration didn't progress. Additional info: ----------------
Depends
https://github.com/konveyor/forklift-controller/pull/146
@fdupont @jortel it does say the target vm name is not valid now but since it is not set by the users, maybe it can be confusing? maybe a better indication to that the issue is with the soure vm name, and this should be fixed in the source.wdty?
What is the name of the VM you're trying to migrate? The message should be "Target VM already exists.", so if you have another message, it means you're hitting another condition.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days