-
Notifications
You must be signed in to change notification settings - Fork 42
Network selection only allow one selection if you add two vCenters to v2v infra map #455
Comments
it seems that we are saying that a {provider}{cluster}{uid_ems} combination uniquely identifies a network instead of just the {uid_ems}. If that is the case, then we probably need to update the logic in both the mapping wizard and the infrastructure mapping list... but it would be nice confirm this before we do that. |
@Yadnyawalkya Are you expecting to see identical Networks for cluster1 and cluster2? |
Updated issue with GIF which explains the issue. @priley86 @AparnaKarve |
@priley86 @michaelkro From the above GIF, it looks like When a mapping is added using I have @Yadnyawalkya 's appliance DB with me locally. Let me know if you need it. |
[#455] use lan id and uid_ems to uniquely identify network
[#455] use lan id and uid_ems to uniquely identify network (cherry picked from commit 2102048) https://bugzilla.redhat.com/show_bug.cgi?id=1599864
Description
Let say, you have to added two vcenter to one infra map.
You can select two clusters, two datastores but only one network.
(Please note network selection is also cluster dependent, same as datastore selection)
Select VM network from cluster1 and then VM network from cluster2 disappear
Version-Release
5.9.3.3.20180627151410_682cecf
How reproducible
100%
Steps to Reproduce
same name
is missing from second cluster listWhat do I mean by 4th step here?
Here for cluster
V2V_Cluster (V2V)
, I mappedvsphere6-lab \ VM Network
torhvm \ VM_Network
and for clusterCluster (V2V)
when I tried to find network, I don't seevsphere6-cfme \ VM Network
. It is not in list.Actual results
Only showing one network
Expected results
Should show two network as clusters are totally different.
Any workaround?
Workaround for this issue will be creating infra-map with single vcenter at source and single rhvm at target (that means using only one cluster at source).
Internal reference
https://bugzilla.redhat.com/show_bug.cgi?id=1596737
The text was updated successfully, but these errors were encountered: