Description of problem:

[*] While performing direct volume migration from OCP v3.11 cluster to OCP v4.7 cluster, the 'rsync-client' container in 'dvm-rsync' pod reports 'Failed' status due to following errors:
~~~
libnsock nsock_make_socket(): Socket trouble: Address family not supported by protocol
libnsock nsock_make_socket(): Socket trouble: Address family not supported by protocol
2021/09/30 08:48:39 [60] rsync: safe_read failed to read 1 bytes [sender]: Connection reset by peer (104)
2021/09/30 08:48:39 [60] rsync error: error in rsync protocol data stream (code 12) at io.c(276) [sender=3.1.3]
rsync: safe_read failed to read 1 bytes [sender]: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(276) [sender=3.1.3]
~~~


Version-Release number of selected component (if applicable):
- MTC v1.5.1
- Migrating from OCP v3.11 to OCP v4.7


How reproducible:
- each time DVM is performed

Actual results:
- DVM reports failed status.

Expected results:
- DVM should be complete without any failures/warnings.


Additional info:
- As we earlier suspected this to be an issue due to `ipv6` being disabled on OCP v3.11 cluster, we tried to append '--ipv4' option to the rsync command in 'rsync-client' container of dvm-rsync pod, as per https://github.com/konveyor/mig-operator/blob/master/docs/usage/RsyncConfiguration.md#performing-a-dry-run (replacing the '--dry-run' with '--ipv4').

- The 'containers[?(.name == "rsync-client")].commands' section has the '--ipv4' appended to the command, but the pod still fails with same error messages.

- The volumes in OCP v3.11 cluster are backed by NFS. Not sure, if this could be the culprit in any way.