Bug 1969760 - [OVS] vdsm should detect the correct openvswitch version
Summary: [OVS] vdsm should detect the correct openvswitch version
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.40.7
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.4.7
: 4.40.70.3
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks: 1940824
TreeView+ depends on / blocked
 
Reported: 2021-06-09 08:28 UTC by Michael Burman
Modified: 2021-07-06 07:28 UTC (History)
3 users (show)

Fixed In Version: vdsm-4.40.70.3
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-06 07:28:15 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 115096 0 None MERGED common, net: Check ovirt-openvswitch package instead of rhv-openvswitch 2021-06-09 08:31:10 UTC

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