networking-ovs-dpdk

DPDK configuration options not removed from ovsdb on unstack

Bug #1656055 reported by David Shaughnessy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovs-dpdk
Confirmed
Medium
Unassigned

Bug Description

These configuration options will cause problems if the node is redeployed with ovs-DPDK enabled.
This issue can be addressed by clearing the database when unstacking.

Revision history for this message
Waldemar Znoinski (wznoinsk) wrote :

that's a legit concern if there's some data from previous deployment

this
https://github.com/openstack/networking-ovs-dpdk/blob/master/devstack/plugin.sh#L62
https://github.com/openstack/networking-ovs-dpdk/blob/master/devstack/libs/ovs-dpdk#L148:L169
should clean bridge and ports

is it not working or is there other data that is the problem?

Revision history for this message
David Shaughnessy (david-shaughnessy) wrote :

Other data, It's the other_config field in the open_vswitch table.

Revision history for this message
sean mooney (sean-k-mooney) wrote :

yes this is an artifact of the db based init.
if you install with ovs-dpdk and then unstack and stack with kernel ovs it fails to delete the entries
in the Open_vSwitch table.

as part of the unstack we should eiter a delete the ovsdb or by null out the dpdk paramaters in the Open_vSwitch table.

Changed in networking-ovs-dpdk:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.