Bug 1969760

Summary:	[OVS] vdsm should detect the correct openvswitch version
Product:	[oVirt] vdsm	Reporter:	Michael Burman <mburman>
Component:	Core	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.40.7	CC:	bugs, dfodor, mperina
Target Milestone:	ovirt-4.4.7	Flags:	pm-rhel: ovirt-4.4+
Target Release:	4.40.70.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	vdsm-4.40.70.3	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-06 07:28:15 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:	1940824

Description Michael Burman 2021-06-09 08:28:13 UTC

Description of problem:
[OVS] vdsm should detect the correct openvswitch version

During testing ovs 2.13/2.15 I have noticed that the openvswitch in the RHV UI manager still reports ovs 2.11, apparently vdsm didn't detected the correct ovs version on the host.

Version-Release number of selected component (if applicable):
vdsm-4.40.70.2-1.el8ev.x86_64
rhvm-4.4.7.1-0.9.el8ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Upgrade to ovs 2.13 or 2.15 from ovs 2.11
2. Refresh caps

Actual results:
RHV UI still shows ovs 2.11

Expected results:
vdsm should detect the right ovs version

Comment 1 Michael Burman 2021-06-14 06:19:33 UTC

Verified on - vdsm-4.40.70.3

Comment 2 Sandro Bonazzola 2021-07-06 07:28:15 UTC

This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021.

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