Bug 1447637

Summary: [RFE] engine should report openvswitch package versions on each host
Product: [oVirt] ovirt-engine Reporter: Mor <mkalfon>
Component: Frontend.WebAdminAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: low    
Version: futureCC: bugs, danken, lsvaty, mburman, myakove, ylavi
Target Milestone: ovirt-4.2.5Keywords: FutureFeature
Target Release: 4.2.5Flags: rule-engine: ovirt-4.2+
mburman: testing_plan_complete-
ylavi: planning_ack+
rule-engine: devel_ack+
mburman: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-31 15:32:26 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:
Attachments:
Description Flags
screenshot none

Description Mor 2017-05-03 11:28:13 UTC
Created attachment 1275883 [details]
screenshot

Description of problem:
Reported of host software versions doesn't show information about openvswitch which is currently dependency of Vdsm.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170429081602.gitb982df7.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Select Vdsm host --> General --> Software

Actual results:
No openvswitch version info is available.

Expected results:
openvswitch version info should be available

Comment 1 Mor 2017-05-03 11:31:18 UTC
This is also relevant for OVN host package, but I am not sure if it should be included in this ticket.

Comment 2 Dan Kenigsberg 2017-11-24 22:35:32 UTC
openvswitch should be included on the Software subtab, with "LIBVIRT Version" etc.

Comment 3 Red Hat Bugzilla Rules Engine 2017-11-24 22:35:38 UTC
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 4 Michael Burman 2018-07-08 07:40:44 UTC
Verified on - 4.2.5.1_SNAPSHOT-71.g54dde01.0.scratch.master.el7ev

Comment 5 Sandro Bonazzola 2018-07-31 15:32:26 UTC
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

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