VolSync rsync mover source does not connect to destination if using an ipv6 address

[tesshuflower]

Describe the bug

If a user creates a replication destination with ClusterIP in an ipv6 env and the address is an ipv6 address - if they use this address in their replicationsource, the replicationsource will not be able to connect to the destination properly.

Workaround is to use the address of the service created by the replication destination instead of the ipv6 address.

Steps to reproduce

• Create a replicationdestination in an ipv6 environment using serviceType: ClusterIP
• The replicationdestination creates a service which has a clusterIP defined in the spec, e.g.

spec:
  clusterIP: fd02::3612
  clusterIPs:
  - fd02::3612

• If this address is used as the address in the replicationsource spec, it will fail to connect.

Workaround is to use the replicationsource service name instead of the ipv6 address. e.g.

 address:  volsync-rsync-dst-database-destination.dest

Expected behavior

Expect the rsync mover to be able to connect to the destination using an ipv6 address.

This may be possible by modifying the mover to connect using:

rsync@[ipv6address]

Note that we cannot simpy direct a user to use something like [fd02::3612] as the address in the replicationsource as this causes the certs to fail checking the remote address which does not match.

Actual results

rsync mover pod on the replicationsource side has logs like this:

VolSync rsync container version: ACM-0.4.1-e6dde1b
Syncing data to fd02::3612:22 ...
rsync: getaddrinfo: fd02 873: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(127) [sender=3.1.3]
Syncronization failed. Retrying in 2 seconds. Retry 1/5.
rsync: getaddrinfo: fd02 873: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(127) [sender=3.1.3]
Syncronization failed. Retrying in 4 seconds. Retry 2/5.
rsync: getaddrinfo: fd02 873: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(127) [sender=3.1.3]
Syncronization failed. Retrying in 8 seconds. Retry 3/5.

Additional context

[tesshuflower]

/assign @tesshuflower

[tesshuflower]

/close

[openshift-ci[bot]]

@tesshuflower: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.