Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1902490

Summary: [MTV][Upstream][AP] Migration plan starts though the mapping contains a wrong source Network id
Product: Migration Toolkit for Virtualization Reporter: Ilanit Stein <istein>
Component: GeneralAssignee: Jeff Ortel <jortel>
Status: CLOSED DUPLICATE QA Contact: Aziza Karol <akarol>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: medium    
Version: 2.0.0CC: fdupont
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-03-10 14:00:13 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:
Description Flags
vm_import_cr_yaml
none
virt-controller.log
none
migration_plan_and_run_api_commands none

Description Ilanit Stein 2020-11-29 15:17:23 UTC 
Description of problem:
Using API, add a Migration plan with one RHEL7 VM using a wrong source network id.
VM import CR is initiated and remain in "import pending" state. 
(The provided source network id is of another network in the source VMware provider, and not the network id of the migrated VM network). 

Version-Release number of selected component (if applicable):
MTV-2.0

Expected results:
Migration plan should fail, and not even start.
Comment 1 Ilanit Stein 2020-11-29 15:18:52 UTC 
Created attachment 1734620 [details]
vm_import_cr_yaml
Comment 2 Ilanit Stein 2020-11-29 15:20:15 UTC 
Created attachment 1734621 [details]
virt-controller.log
Comment 3 Ilanit Stein 2020-11-29 15:24:11 UTC 
Created attachment 1734622 [details]
migration_plan_and_run_api_commands
Comment 4 Fabien Dupont 2021-03-10 14:00:13 UTC 
The expected behavior is identical to BZ 1902487, but for network. Closing to keep things clear from a development perspective.

*** This bug has been marked as a duplicate of bug 1902487 ***