Bug 1779727 - Open vSwitch based physical_network does not work
Summary: Open vSwitch based physical_network does not work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.40.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.4.4
: 4.40.38
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1695115 1809102
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 15:24 UTC by Dominik Holler
Modified: 2020-12-21 12:35 UTC (History)
1 user (show)

Fixed In Version: vdsm-4.40.38-1.el8ev.x86_64
Clone Of:
Environment:
Last Closed: 2020-12-21 12:35:56 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 112048 0 None MERGED net, ovs: Configure OvS bridge mappings 2021-01-13 17:07:06 UTC

Internal Links: 1809102

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