Comment 4 for bug 2067889

Again, is that the root cause or a symptom of a former failure?
Not all tests are very clear in that regard, but one I liked.
As it fails BEFORE this cleanup phase.

The "MTU upper bound vport port" test is like this:

> 2024-05-31T10:08:28.364Z|00117|netdev_dpdk|WARN|dpdkvhostuserclient0: unsupported MTU 9711
> 2024-05-31T10:08:28.364Z|00118|netdev|WARN|failed to set MTU for network device dpdkvhostuserclient0: Invalid argument
> 2024-05-31T10:08:28.374Z|00119|bridge|INFO|bridge br10: deleted interface dpdkvhostuserclient0 on port 1
> 2024-05-31T10:08:28.374Z|00120|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 3 destroyed.
> 2024-05-31T10:08:28.374Z|00002|dpdk(pmd-c03/id:10)|INFO|PMD thread released DPDK lcore 1.
> 2024-05-31T10:08:28.375Z|00121|dpdk|INFO|VHOST_CONFIG: (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0) free connfd 52
> 2024-05-31T10:08:28.375Z|00122|netdev_dpdk|INFO|vHost Device '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0' not found
tests/system-dpdk-testsuite: line 1754: 275858 Killed dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
20. system-dpdk.at:736: 20. OVS-DPDK - MTU upper bound vport port (system-dpdk.at:736): FAILED (system-dpdk.at:767)

But this is a red-herring, as the setting of this is meant to fail.
The test says:
  "Set MTU value above upper bound and check for error"

So it might indeed be the cleanup that fails?