Bug 1887813 - [CNV][V2V] Default network type is bridge for interface bound to POD network in VMWare migration wizard
Summary: [CNV][V2V] Default network type is bridge for interface bound to POD network ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.6.z
Assignee: Filip Krepinsky
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On: 1887797
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-13 12:22 UTC by Tomas Jelinek
Modified: 2021-02-22 13:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Automatic selection of network type for pod networks in v2v import.
Clone Of: 1887797
Environment:
Last Closed: 2021-02-22 13:54:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Target VM network screenshot (27.95 KB, image/png)
2021-02-11 18:39 UTC, Ilanit Stein
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6936 0 None closed [release-4.6.z] Bug 1887813: assign masquerade to pod interface in RHV import 2021-02-16 06:35:29 UTC
Red Hat Product Errata RHBA-2021:0510 0 None None None 2021-02-22 13:54:49 UTC

Description Tomas Jelinek 2020-10-13 12:22:48 UTC
+++ This bug was initially created as a clone of Bug #1887797 +++

Description of problem: Default network type is bridge for interface bound to POD network. When running wizard user needs to update network setting to masquerading manually


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


How reproducible: 100%


Steps to Reproduce:
1. Run migration wizard from VMWare to CNV
2. Go to the network settings of VM
3. Open NIC that is bound to POD network

Actual results: Bridged network type is selected by default regardless it is not supported


Expected results: Masquerade network type should be default


Additional info:

--- Additional comment from Fabien Dupont on 2020-10-13 12:10:09 UTC ---

Tomas, is there still time to fix it for CNV 2.5.0?

--- Additional comment from Tomas Jelinek on 2020-10-13 12:21:03 UTC ---

I'll move it under UI and target 4.6.z

Comment 1 Yaacov Zamir 2020-12-09 07:52:45 UTC
Can't merge this fix until it's verified on 4.7, BZ1887797

https://bugzilla.redhat.com/show_bug.cgi?id=1887797 - is currently ON_QA

Comment 2 Yaacov Zamir 2021-01-27 06:39:41 UTC
Update:
1887797 verified
https://github.com/openshift/console/pull/6936 updated according to fix of 1887797 and is waiting for cherry-pick approval

Comment 6 Ilanit Stein 2021-02-11 18:38:27 UTC
Verified on OCP-4.6.16/CNV-2.5.4

See "Target VM network screenshot" attached.

Comment 7 Ilanit Stein 2021-02-11 18:39:53 UTC
Created attachment 1756452 [details]
Target VM network screenshot

Comment 10 errata-xmlrpc 2021-02-22 13:54:32 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 (OpenShift Container Platform 4.6.18 bug fix update), 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/RHBA-2021:0510


Note You need to log in before you can comment on or make changes to this bug.