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

Bug 1995407

Summary: [Doc] Resolve ambiguity for RHV in case of more than one cluster/data center.
Product: Migration Toolkit for Virtualization Reporter: Ilanit Stein <istein>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED NEXTRELEASE QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact: Avital Pinnick <apinnick>
Priority: high    
Version: 2.1.0CC: amastbau, apinnick, fdupont, istein, jortel
Target Milestone: ---   
Target Release: 2.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1993089 Environment:
Last Closed: 2021-08-22 13:50:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1993089    
Bug Blocks:    

Description Ilanit Stein 2021-08-19 03:16:43 UTC 
Please document the below as a known issue for MTV-2.1. It is targeted to MTV-2.2.

+++ This bug was initially created as a clone of Bug #1993089 +++

Description of problem:

When migration from RHV and creating a Mapping or Plan CR, the users can either specify the id or the name of the resource (storage, network or VM).

However, using the name of the resource can lead to ambiguous specification, as multiple resources of the same type and with the same name can exist in different scopes.

In RHV, a storage domain, network or virtual machine is unique within the datacenter scope. So, to remove the ambiguity, it should be possible to set the datacenter is the CR spec.
Comment 2 Ilanit Stein 2021-08-19 14:16:17 UTC 
When we have, For Example, 2 datacenters both have 1 network each name ovirtmgmt:

In the UI: 
When creating a Network Map Outside the migration wizard - see net_map.png:
But once you create the mapping everything works correctly 

In the API:
The plan CR is in Critical condition (not possible to run the plan):

apiVersion: forklift.konveyor.io/v1beta1
kind: NetworkMap
metadata:
  creationTimestamp: "2021-08-12T06:19:40Z"
  generation: 1
  name: blue-name
  namespace: openshift-mtv
  resourceVersion: "60985886"
  uid: 808322f3-a952-427a-94bc-8c6ca35570da
spec:
  map:
  - destination:
      type: pod
    source:
      name: vm/vm
  - destination:
      name: ovn-secondnetwork
      namespace: amos
      type: multus
    source:
      name: MTV/ovirtmgmt/ovirtmgmt
  provider:
    destination:
      name: host
      namespace: openshift-mtv
    source:
      name: rhv-blue-amos
      namespace: openshift-mtv
status:
  conditions:
  - category: Critical
    items:
    - ' id: name:''MTV/ovirtmgmt/ovirtmgmt'' '
    lastTransitionTime: "2021-08-12T06:31:13Z"
    message: Source network has ambiguous ref.
    reason: Ambiguous
    status: "True"
    type: SourceNetworkNotValid
  observedGeneration: 1


Workarounds:
1. In API use IDs and not names, in case of names ambiguity.
2. Rename the component (like network for example) that has an ambiguous name.
Comment 5 Avital Pinnick 2021-08-22 13:50:57 UTC 
Changes verified and merged.