Description of problem:
When running a VM latency checkup, I get a warning saying that 'Write failed: io: read/write on closed pipe'.

Version-Release number of selected component (if applicable):
$ oc get csv -A | grep virt
openshift-cnv kubevirt-hyperconverged-operator.v4.14.0 OpenShift Virtualization 4.14.0 kubevirt-hyperconverged-operator.v4.13.4 Succeeded

$ oc get clusterversion git:(add_checkup_tests|✚4…10⚑31
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.14.0-rc.6 True False 3d Cluster version is 4.14.0-rc.6

How reproducible:

Steps to Reproduce:
Steps to Reproduce:
1. Create a VM latency checkup following the steps in the documentation:
https://docs.openshift.com/container-platform/4.13/virt/support/monitoring/virt-running-cluster-checkups.html#virt-measuring-la[%E2%80%A6]g-cluster-checkups
2. Check the logs of the pod created by the job.
3.

Actual results:
$ oc logs pod/default-latency-job-1-k8nwc
— 10.24.171.45 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 9.635/31.123/81.013 ms
latency-check-source-d7rdf:~#
PING 10.24.171.45 (10.24.171.45): 56 data bytes
64 bytes from 10.24.171.45: seq=0 ttl=64 time=81.013 ms
64 bytes from 10.24.171.45: seq=1 ttl=64 time=34.014 ms
64 bytes from 10.24.171.45: seq=2 ttl=64 time=16.417 ms
64 bytes from 10.24.171.45: seq=3 ttl=64 time=14.536 ms
64 bytes from 10.24.171.45: seq=4 ttl=64 time=9.635 ms

— 10.24.171.45 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 9.635/31.123/81.013 ms
latency-check-source-d7rdf:~ # ]}
2023/10/26 11:45:38 ping parser: failed to parse 'time': time: invalid duration "ms"
2023/10/26 11:45:38 deleting VMI test-checkup-framework/latency-check-source-d7rdf..
2023/10/26 11:45:38 Write failed: io: read/write on closed pipe
2023/10/26 11:45:38 read closing down: EOF

Expected results:

Additional info: