Bug 1986020 - [MTV][API<>UI] Invalid network/storage mapping when using source.name instead of ID, duplicate/edit plan breaks when using VMs or mapping items by name instead of ID
Summary: [MTV][API<>UI] Invalid network/storage mapping when using source.name instead...
Keywords:
Status: ASSIGNED
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: General
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.4.0
Assignee: Michael Spaxman
QA Contact: Maayan Hadasi
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks: 2023801
TreeView+ depends on / blocked
 
Reported: 2021-07-26 14:17 UTC by Maayan Hadasi
Modified: 2022-01-20 10:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2023801 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
UI screenshot (66.98 KB, image/png)
2021-07-26 14:17 UTC, Maayan Hadasi
no flags Details

Description Maayan Hadasi 2021-07-26 14:17:02 UTC
Created attachment 1805939 [details]
UI screenshot

Description of problem:
Once using source.name within mappings -> the mapping is invalid in UI, though the mapping CR is ready  


Version-Release number of selected component (if applicable):
mtv-operator-bundle-container-2.1.0-31


How reproducible:
100%


Attachments:
UI screenshot
NetworkMap yaml

Comment 2 Fabien Dupont 2021-08-04 12:46:51 UTC
This is not a blocker bug, so targeting to 2.2.0.

Comment 3 Mike Turley 2021-11-01 17:51:11 UTC
@fdupont@redhat.com would it be okay to move this one to 2.3.0? Mike S started working on it and I think it's ok to wait until he's back to finish it. The issue is not reproducible for mappings created using the UI, it only happens if you create mappings with the CLI/API using name instead of id and then view them in the UI.

Comment 4 Fabien Dupont 2021-11-08 11:21:47 UTC
Not a blocker for MTV 2.2.0. Changing target release to 2.3.0.

Comment 5 Mike Turley 2021-11-16 15:04:13 UTC
Note: this applies to VMs in the plan spec as well. Both VMs and mapping items in the spec of the CRs should support using either name or id.

Comment 6 Mike Turley 2021-11-16 15:14:47 UTC
Further details: a CR in this state will also cause "duplicate plan" and "edit plan" features in the UI to break. The wizard will fail to look up the VMs and mapping items from the spec and certain wizard steps will fail to initialize properly.

Comment 7 Maayan Hadasi 2022-01-20 10:52:48 UTC
Updating that this issue breaks also the "View plan details" in UI - 
The selected VMs/source networks/source datastores are not listed when creating the MTV CRs using names instead of IDs


Note You need to log in before you can comment on or make changes to this bug.