Bug 1698435
Summary: | glusterfs-libs: usage of inet_addr() may impact IPv6 | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Milind Changire <mchangir> | |
Component: | core | Assignee: | Rinku <rkothiya> | |
Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | rhgs-3.5 | CC: | amukherj, nchilaka, rhs-bugs, rkothiya, sasundar, sheggodu, storage-qa-internal, vdas | |
Target Milestone: | --- | |||
Target Release: | RHGS 3.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-6.0-8 | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1721385 (view as bug list) | Environment: | ||
Last Closed: | 2019-10-30 12:20:50 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: | 1696809, 1721385 |
Description
Milind Changire
2019-04-10 11:17:15 UTC
REVIEW: https://review.gluster.org/#/c/glusterfs/+/22866/ (core: replace inet_addr with inet_pton) posted (#1) for review on master by Rinku Kothiya We saw this error popping up in eventing component which is used in RHHI. So recommend fixing it. Tested with glusterfs-6.0-15.el7rhgs 1. RHGS nodes are set with pure IPV6 2. Glusterd configured to support inet v6 3. Gluster peer probe done with IPv6 4. Gluster volume is created with the same IPV6 5. Gluster volume is fuse mounted with special mount option and then I/O done. 6. Geo-rep session also initiated and completed to another gluster IPv6 cluster No errors seen. 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:3249 |