In some environments, ovs-vswitchd gets shutdown before the pkill of testpmd has been completed, which results in the following error messages:
Removing port 'dpdkvhostuser0' while vhost device still attached. To restore connectivity after re-adding of port, VM on socket '' must be restarted. This patch will wait for the socket disconnect to be handled by the vhost-user before shutting down OVS. Signed-off-by: Eelco Chaudron <[email protected]> Signed-off-by: David Marchand <[email protected]> Co-authored-by: David Marchand <[email protected]> --- v2: Used sync point rather than ignoring the messages. tests/system-dpdk.at | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tests/system-dpdk.at b/tests/system-dpdk.at index 8dc187a61..5301b6b56 100644 --- a/tests/system-dpdk.at +++ b/tests/system-dpdk.at @@ -154,6 +154,9 @@ AT_CHECK([ip netns exec ns1 ping -c 4 -I tap0 172.31.110.12], [], [stdout], dnl Clean up the testpmd now pkill -f -x -9 'tail -f /dev/null' +dnl Wait for vhost-user handling the socket disconnect. +OVS_WAIT_UNTIL([grep "vHost Device '$OVS_RUNDIR/dpdkvhostuser0' has been removed" ovs-vswitchd.log]) + dnl Clean up AT_CHECK([ovs-vsctl del-port br10 dpdkvhostuser0], [], [stdout], [stderr]) OVS_VSWITCHD_STOP("m4_join([], [SYSTEM_DPDK_ALLOWED_LOGS], [ _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
