Bug 1532719

Summary:	Show DPDK version in OpenvSwitch
Product:	Red Hat Enterprise Linux 7	Reporter:	Matteo Croce <mcroce>
Component:	openvswitch	Assignee:	Matteo Croce <mcroce>
Status:	CLOSED ERRATA	QA Contact:	Jean-Tsung Hsiao <jhsiao>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	atragler, ctrautma, fleitner, pvauter, tli, tredaelli
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	openvswitch-2.9.0-1.el7fdp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-19 10:22:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1475436

Description Matteo Croce 2018-01-09 16:27:33 UTC

Description of problem:

Actually OpenvSwitch doesn't have any command to show the DPDK version it was linked against.
People are forces to do "strings `which ovs-vswitchd` |grep dpdk-" to get the DPDK version.


Version-Release number of selected component (if applicable):
2.9 with DPDK 17.11

upstream discussion:

https://mail.openvswitch.org/pipermail/ovs-dev/2017-December/342359.html

Comment 2 Matteo Croce 2018-01-16 11:09:47 UTC

Patch posted

https://mail.openvswitch.org/pipermail/ovs-dev/2018-January/343254.html

Comment 3 Matteo Croce 2018-01-23 16:20:21 UTC

merged in Ian Stokes's dpdk_merge_2_9 tree

Comment 7 Christian Trautman 2018-02-20 12:51:01 UTC

Verified with openvswitch-2.9.0-1.el7fdp.x86_64.rpm

Comment 8 Christian Trautman 2018-03-11 21:54:08 UTC

[root@netqe22 ~]# ovs-vswitchd --version
ovs-vswitchd (Open vSwitch) 2.9.0
DPDK 17.11.0
[root@netqe22 ~]#

Comment 11 errata-xmlrpc 2018-03-19 10:22:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0550