Bug 1953555

Summary: GlusterFS tests fail on ipv6 clusters
Product: OpenShift Container Platform Reporter: Jan Safranek <jsafrane>
Component: StorageAssignee: Jan Safranek <jsafrane>
Storage sub component: Kubernetes QA Contact: Wei Duan <wduan>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs
Version: 4.8   
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 23:03:38 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:

Description Jan Safranek 2021-04-26 11:33:36 UTC
All GlusterFS e2e tests fail on IPv6 machines:

E [MSGID: 101075] [common-utils.c:312:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Address family for hostname not supported)
E [name.c:267:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host fd01:0:0:5::56
I [glusterfsd-mgmt.c:2348:mgmt_rpc_notify] 0-glusterfsd-mgmt: disconnected from remote-host: fd01:0:0:5::56

We do not support GlusterFS in-tree volume plugin in OCP 4.x, we run the tests just because we can. Now it's IMO time to finally remove the tests from our CI.

Comment 1 Jan Safranek 2021-04-26 11:38:33 UTC
Note: this will need to be updated in openshift/origin too.

Comment 6 Jan Safranek 2021-05-26 13:24:48 UTC
This should be fixed by https://github.com/openshift/origin/pull/26178

Comment 8 Wei Duan 2021-06-01 02:01:59 UTC
Verified pass, these cases are not be executed in 4.8.

Comment 11 errata-xmlrpc 2021-07-27 23:03:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.