integration: fix MTU checking for OVS>=2.9 72/68672/3
authorLukasz Pawlik <lukaszx.pawlik@intel.com>
Fri, 4 Oct 2019 12:27:09 +0000 (13:27 +0100)
committerEmma Finn <emma.finn@intel.com>
Tue, 29 Oct 2019 11:04:36 +0000 (11:04 +0000)
commit2901426e488e91ce3d90690e834c697148b6de7c
treecf3a612a75990f4522b2663a6484f6393df16c9f
parent755894494dc58e093d7376bf41f15dcbbdb5e53b
integration: fix MTU checking for OVS>=2.9

In DPKD>=17.11.0 and OVS>=2.9 behaviour of MTU has changed. Previously
ovsdpdk_jumbo_p2p_upper_bound checked that two different MTU could be
set for a port in OVS DPDK. However due to changes in OVS a larger MTU
value is now required to create different mempools. Fix this by
increasing the MTU value requested so that a new mempool will be
created. Also output for calls to ovs-appctl has changed. This commit
fixes the expected regex to account for new spaces and reformat of the
queue listings in open vSwtich.
List of fixed tests:
ovsdpdk_mq_p2p_rxqs
ovsdpdk_mq_p2p_rxqs_same_core_affinity
ovsdpdk_mq_p2p_rxqs_multi_core_affinity
ovsdpdk_mq_pvp_rxqs
ovsdpdk_mq_pvp_rxqs_testpmd
ovsdpdk_jumbo_mtu_upper_bound_phy_port
ovsdpdk_jumbo_mtu_upper_bound_vport
ovsdpdk_jumbo_p2p_upper_bound

Co-authored-by: Ian Stokes <ian.stokes@intel.com>
Change-Id: I22e208004e5b732b4b21904809606055fbb9c0c4
Signed-off-by: Lukasz Pawlik <lukaszx.pawlik@intel.com>
conf/integration/01b_dpdk_regression_tests.conf