Bug 2012979

Summary:	During DVM rsync-client reports 'Address family not supported by protocol'
Product:	Migration Toolkit for Containers	Reporter:	Apoorva Jagtap <apjagtap>
Component:	Controller	Assignee:	John Matthews <jmatthew>
Status:	CLOSED WONTFIX	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	1.5.1	CC:	ernelson, jmatthew, rjohnson
Target Milestone:	---
Target Release:	1.5.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2021630 2028841 (view as bug list)		Environment:
Last Closed:	2021-12-16 21:46:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2021630, 2028841

Description Apoorva Jagtap 2021-10-11 18:43:40 UTC

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.

Comment 3 Erik Nelson 2021-11-10 02:56:47 UTC

*** Bug 2021630 has been marked as a duplicate of this bug. ***

Comment 8 Erik Nelson 2021-12-16 21:46:25 UTC

Closing as WONTFIX as we are no longer planning a 1.5.4 release given its proximity with the 1.7 release, which is the date that 1.5 will fall out of support (2/16/22).