Bug 1887813

Summary: [CNV][V2V] Default network type is bridge for interface bound to POD network in VMWare migration wizard
Product: OpenShift Container Platform Reporter: Tomas Jelinek <tjelinek>
Component: Console Kubevirt PluginAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: high    
Version: 4.6CC: aos-bugs, cnv-qe-bugs, fdupont, fkrepins, gouyang, ibragins, istein, tjelinek, yzamir
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Automatic selection of network type for pod networks in v2v import.
 Story Points: ---
Clone Of: 1887797 Environment:
Last Closed: 2021-02-22 13:54:32 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: 1887797    
Bug Blocks:    
Attachments:
Description Flags
Target VM network screenshot none

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