What were you trying to do that didn't work?

When several OpenShift virt CDI host-assisted clones from the same PVC are done concurrently, the source volume files (including disk.img) ctime may change during the operation, so tar fails and the pod is restarted:

clone-source.go:41] Subprocess did not execute successfully, result is: '\x01'
/usr/bin/tar: disk.img: file changed as we read it

The issue happens with the current tar version 1.34, and seems to be solved in 1.35:

* Warn file changed as we read it less often. Formerly, tar warned if the file's size or ctime changed. However, this generated a false positive if tar read a file while another process hard-linked to it, changing its ctime.
* Fix --ignore-failed-read to ignore file-changed read errors as far as exit status is concerned. You can now suppress file-changed issues entirely with --ignore-failed-read --warning=no-file-changed.

We tested it by explicitly using rhel10 stream tar 1.35. It depends on newer glibc (glibc-2.39-15.el10.x86_64.rpm), so we added it as well.

Since we are based on the rhel9 stream, we would like to have tar 1.35 rpm backport build there to solve the issue, as well of the required glibc (unless a static build is provided). 

Please provide the package NVR for which bug is seen:

tar-2__1.34-6.el9.x86_64

How reproducible:

100%

Steps to reproduce

Expected results

Actual results