Bug 1428014 - Restart openvswitch after adding DPDK ports
Summary: Restart openvswitch after adding DPDK ports
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: z3
: 10.0 (Newton)
Assignee: Saravanan KR
QA Contact: Yariv
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 17:26 UTC by Saravanan KR
Modified: 2017-06-28 14:46 UTC (History)
6 users (show)

Fixed In Version: os-net-config-5.1.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-28 14:46:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1668375 0 None None None 2017-03-01 17:26:37 UTC
OpenStack gerrit 439519 0 None None None 2017-03-01 17:28:13 UTC
Red Hat Product Errata RHBA-2017:1585 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 director Bug Fix Advisory 2017-06-28 18:42:51 UTC

Description Saravanan KR 2017-03-01 17:26:37 UTC 
DPDK initialization will be done before running the NetworkDeployment (os-net-config). Inorder to make the DPDK port ready, after binding the DPDK driver, openvswitch need to be restarted, because opevswitch 2.5 and 2.6 does not support HOT plug. So for now, restart ovs after adding the DPDK port.

HOT plug support is available in ovs2.7 version only.
Comment 2 Yariv 2017-03-21 12:37:34 UTC 
This Bug Should with fresh RHOS 10 with OVS 2.6
Comment 3 Ziv Greenberg 2017-03-21 14:35:39 UTC 
Hi,

It was verified with a clean install of OSPD10 with OVS 2.6 and os-net-config-5.1.0-2.el7ost

Thanks,
Ziv
Comment 5 errata-xmlrpc 2017-06-28 14:46:07 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-2017:1585
Note You need to log in before you can comment on or make changes to this bug.