Bug 1897284

Summary: Premigration check to ensure source VMs do not already exist on the target provider
Product: Migration Toolkit for Virtualization Reporter: Nandini Chandra <nachandr>
Component: GeneralAssignee: Jeff Ortel <jortel>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: high    
Version: 2.0.0CC: amastbau, fdupont, jortel
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:26 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 Nandini Chandra 2020-11-12 17:19:20 UTC 
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:
----------------
Comment 1 Fabien Dupont 2020-11-24 18:08:34 UTC 
Depends
Comment 2 Jeff Ortel 2021-01-27 21:45:11 UTC 
https://github.com/konveyor/forklift-controller/pull/146
Comment 3 Amos Mastbaum 2021-04-25 15:29:42 UTC 
@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?
Comment 4 Fabien Dupont 2021-04-30 06:50:59 UTC 
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.
Comment 7 errata-xmlrpc 2021-06-10 17:11:26 UTC 
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
Comment 8 Red Hat Bugzilla 2023-09-15 00:51:06 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days