Bug 1809102

Summary:	Enable OVS switch type for nmstate managed hosts
Product:	[oVirt] vdsm	Reporter:	Dominik Holler <dholler>
Component:	Core	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.40.5	CC:	amusil, bugs, eslutsky, mperina
Target Milestone:	ovirt-4.4.3	Flags:	pm-rhel: ovirt-4.4+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.3.7, vdsm-4.40.33	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:39:28 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:
Bug Blocks:	1195208, 1779727

Description Dominik Holler 2020-03-02 12:35:27 UTC

Description of problem:
Currently the OVS switch type does not work on nmstate managed hosts.

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

How reproducible:


Steps to Reproduce:
1. 
2. 
3.

Actual results:


Expected results:


Additional info:

Comment 1 Sandro Bonazzola 2020-06-01 09:52:02 UTC

Raising severity to high. This is causing troubles in OCP on oVirt CI environment when running on oVirt 4.4.
If this is not going to be fixed quickly we'll need to find an alternative or we won't be able to support OCP on oVirt 4.4.

Comment 2 Evgeny Slutsky 2020-06-01 11:59:44 UTC

from my tests it is possible to use OVS on 4.4 hosts, although it's blocked by the engine UI, it's possible to migrate the host from linuxbridge to OVStype cluster.
can we support such scenarios?

Comment 3 Dominik Holler 2020-06-02 09:07:28 UTC

(In reply to Evgeny Slutsky from comment #2)
> from my tests it is possible to use OVS on 4.4 hosts, although it's blocked
> by the engine UI, it's possible to migrate the host from linuxbridge to
> OVStype cluster.

The host might be in a bad state after migration.

> can we support such scenarios?

We plan to address OVS cluster type, but not in the next three weeks.

Comment 4 Sandro Bonazzola 2020-10-07 11:33:09 UTC

All patches seems to be already merged, anything else before moving to MODIFIED?

Comment 5 Ales Musil 2020-10-07 12:23:28 UTC

(In reply to Sandro Bonazzola from comment #4)
> All patches seems to be already merged, anything else before moving to
> MODIFIED?

We still need an ack on engine bug then it can be moved.

Comment 6 Michael Burman 2020-10-25 14:06:47 UTC

Verified on - rhvm-4.4.3.8-0.1.el8ev.noarch with 
vdsm-4.40.35-1.el8ev.x86_64
nmstate-0.3.4-13.el8_3.noarch
NetworkManager-1.26.0-9.el8_3.x86_64

Tested:

1. Add fresh host to OVS switch type cluster
2. Move host from legacy switch type cluster to OVS switch type cluster and vise versa (manual sync required)
3. Create bond
4. Attach networks to NIC/BOND, including vlan network
5. Set static IPv4/6 addresses
6. Start VM with physnet external network(Vms got IPv4 from OVN dhcp and can ping each other)

Comment 7 Sandro Bonazzola 2020-11-11 06:39:28 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.