Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1753232

Summary:	Default example VM has bridge NIC binding method instead of masquerade
Product:	OpenShift Container Platform	Reporter:	Radim Hrazdil <rhrazdil>
Component:	Console Kubevirt Plugin	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED ERRATA	QA Contact:	Radim Hrazdil <rhrazdil>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, gouyang, ncredi, tjelinek
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.3.0-0.nightly-2019-11-12-043446	Doc Type:	Bug Fix
Doc Text:	Changed the default NIC binding method to masquerade instead of 'bridge'	Story Points:	---
Clone Of:
Clones:	1757751 (view as bug list)		Environment:
Last Closed:	2020-01-23 11:06:16 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:
Bug Depends On:
Bug Blocks:	1757751

Description Radim Hrazdil 2019-09-18 12:58:38 UTC

Description of problem:
When VM is created using the default YAML example, the VM has a NIC binding method 'bridge' for Pod Networking instead of 'masquerade' which should be default.

In VM wizard, masquerade is the default binding method, which is correct.


Version-Release number of selected component (if applicable):
HCO-47
4.2.0-0.nightly-2019-09-17-232025

How reproducible:
100%

Steps to Reproduce:
1. Create VM via YAML page using default manifest
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tomas Jelinek 2019-09-23 10:36:56 UTC

No way this will make 4.2. Can you please target 4.3?

Comment 3 Guohua Ouyang 2019-11-25 03:10:09 UTC

verified the bug on 4.3.0-0.nightly-2019-11-21-122827

Comment 5 errata-xmlrpc 2020-01-23 11:06:16 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, 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-2020:0062