Bug 1952636

Summary: Migration network selection list does not show the default migration network defined for the target provider
Product: Migration Toolkit for Virtualization Reporter: Ilanit Stein <istein>
Component: User ExperienceAssignee: Mike Turley <mturley>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact: Avital Pinnick <apinnick>
Priority: high    
Version: 2.0.0CC: apinnick, dagur, fdupont, istein, mturley
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-06-10 17:11:46 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
network help message
none
networks list
none
Openshift cluster defined network none

Description Ilanit Stein 2021-04-22 17:39:09 UTC 
Description of problem:
Have OCP cluster that has 2 networks: Pod and ovn-kubernetes1(multus).
The ovn-kubernetes1 network was added within "default" namespace.
Define a default migration network for the "host" OpenShift Virtualization provider as ovn-kubernetes1. 

In the migration plan creation dialog, after picking default namespace, the selected Openshift network displayed is POD, _though_ ovn-kubernetes1 was defined.
It is possible to select from the networks list ovn-kubernetes1.

This contradicts the help message besides the network:
"The default migration network defined for the OpenShift Virtualization provider is used if it exists in the target namespace. Otherwise, the pod network is used. You can select a different network for this migration plan."  

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

Expected results:
Openshit network should be as defined for the Openshift provider.
Comment 1 Ilanit Stein 2021-04-22 17:49:52 UTC 
Created attachment 1774583 [details]
network help message
Comment 2 Ilanit Stein 2021-04-22 17:50:38 UTC 
Created attachment 1774584 [details]
networks list
Comment 3 Ilanit Stein 2021-04-22 17:51:50 UTC 
Created attachment 1774585 [details]
Openshift cluster defined network
Comment 4 Mike Turley 2021-04-26 15:07:08 UTC 
@istein, this is working as intended in my dev environment. Something must be different in your cluster. Do you have login details you can share?
Comment 6 Mike Turley 2021-04-26 22:36:19 UTC 
Found the cause, the inventory API data doesn't quite match up with what my code assumed (it is missing the `metadata.annotations` property on providers). Not sure if it broke because of backend changes or if I missed it in testing. This PR changes the code to load the full CR for this lookup, which fixes the bug: https://github.com/konveyor/forklift-ui/pull/557
Comment 7 Fabien Dupont 2021-05-03 12:09:38 UTC 
The fix should be part of build mtv-operator-bundle-container-2.0.0-4 / iib:72115.
Comment 8 Ilanit Stein 2021-05-05 07:12:05 UTC 
Verified on mtv-operator-bundle-container-2.0.0-4
Comment 11 errata-xmlrpc 2021-06-10 17:11:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (MTV 2.0.0 images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:2381