Comment 18 for bug 2067889

Here the differences I spot on a high level:

4. OVS-DPDK - ping vhost-user ports
 - testpmd.log - not much difference
 - ovsdb-server.log
   ovsdb-server is killed (sig 15) in the bad case 7 seconds after starting
   that kill is after the test log ends, so it could be cleanup
 - ovs-vswitchd.log
   dpdk|ERR|TELEMETRY: Socket write base info to client failed (likely red herring)
   in addition to all-same messages like the good case, the bad case shows
   dpdk|ERR|remove_xdp_program(): bpf_xdp_query_id failed
   dpdk|ERR|eth_dev_close(): Error while removing XDP program.
 - system-dpdk-testsuite.log
   differs at the end, good case seems to enter cleanup while bad case does lots of things
   bad case has more content as it reports detailed steps
   can't cleanup testpmd (pid already gone)

16. OVS-DPDK - MTU increase vport port
17. OVS-DPDK - MTU decrease vport port (same)
20. OVS-DPDK - MTU upper bound vport port (same)
21. OVS-DPDK - MTU lower bound vport port (same)
 - testpmd.log
   good case sees ports going down and stopping
 - ovsdb-server.log
      ovsdb-server is killed (sig 15) in the bad case a few seconds after starting
      that kill is after the test log ends, so it could be cleanup
 - ovs-vswitchd.log
      dpdk|ERR|TELEMETRY: Socket write base info to client failed (likely red herring)
 - system-dpdk-testsuite.log
   differs at the end, good case seems to enter cleanup while bad case does lots of things
   bad case has more content as it reports detailed steps
   can't cleanup testpmd (pid already gone)

So on case 4 it could be the xdp error which is new.
On the other cases only the telemetry is odd, but that seemed (see above) like a false positive.
Yet there are chances a component I didn't see yet tests on no ERR messages.
Worth a rebuild with this reverted?