DPDK configuration options not removed from ovsdb on unstack

[David Shaughnessy]

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.

[Waldemar Znoinski (wznoinsk)]

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?

[David Shaughnessy (david-shaughnessy)]

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

[sean mooney (sean-k-mooney)]

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.