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

Bug 1779727

Summary:	Open vSwitch based physical_network does not work
Product:	[oVirt] vdsm	Reporter:	Dominik Holler <dholler>
Component:	Core	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.40.0	CC:	bugs
Target Milestone:	ovirt-4.4.4	Flags:	pm-rhel: ovirt-4.4+
Target Release:	4.40.38
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm-4.40.38-1.el8ev.x86_64	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-21 12:35:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1695115, 1809102
Bug Blocks:

Description Dominik Holler 2019-12-04 15:24:25 UTC

Description of problem:
Connecting a physical interface to a OVS switch is not working if VDSM uses nmstate.

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


How reproducible:


Steps to Reproduce:
1. Create an external network with provider:physical_network on ovirt-provider-ovn
2. Connect the related vNIC profile in oVirt to a VM
3. Run the VM on a host which is managed by VDSM with nmstate

Actual results:
VM has no network connectivity

Expected results:
VM has network connectivity

Additional info:
All tests in network-suite-master/tests/ovs/test_ovn_physnet.py should pass.

Comment 1 Michael Burman 2020-12-01 07:57:28 UTC

Verified on - vdsm-4.40.38-1.el8ev.x86_64 and rhvm-4.4.4.2-0.1.el8ev.noarch

Comment 2 Sandro Bonazzola 2020-12-21 12:35:56 UTC

This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE.

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