Bug 1952636 - Migration network selection list does not show the default migration network defined for the target provider
Summary: Migration network selection list does not show the default migration network ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: User Experience
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.0.0
Assignee: Mike Turley
QA Contact: Ilanit Stein
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-22 17:39 UTC by Ilanit Stein
Modified: 2021-06-24 08:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-10 17:11:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
network help message (82.70 KB, image/png)
2021-04-22 17:49 UTC, Ilanit Stein 		no flags Details
networks list (87.45 KB, image/png)
2021-04-22 17:50 UTC, Ilanit Stein 		no flags Details
Openshift cluster defined network (49.40 KB, image/png)
2021-04-22 17:51 UTC, Ilanit Stein 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github konveyor forklift-ui pull 557 0 None open Bug 1952636: Use the provider CR instead of the inventory provider to look for the defaultTransferNetwork annotation in ... 2021-04-26 22:26:44 UTC
Red Hat Product Errata RHEA-2021:2381 0 None None None 2021-06-10 17:11:57 UTC

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
Note You need to log in before you can comment on or make changes to this bug.