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
This is not a blocker bug, so targeting to 2.2.0.
@fdupont 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.
Not a blocker for MTV 2.2.0. Changing target release to 2.3.0.
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.
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.
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
*** This bug has been marked as a duplicate of bug 2067708 ***
This issue was verified as Fixed. Versions: MTV-2.3.2-7 / iib:261342 CNV-4.10.3-4 / iib:257615