Bug 1449076

Summary: [RHEL6] glusterd crashes when peering an IP where the address is more than acceptable range (>255) OR with random hostnames
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Atin Mukherjee <amukherj>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Bala Konda Reddy M <bmekala>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: amukherj, asoman, bmekala, mchangir, nchilaka, rcyriac, rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.2.0 Async   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-18.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1440162 Environment:
Last Closed: 2017-06-08 09:37:20 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: 1433276, 1433578, 1434399, 1440162    
Bug Blocks:    

Comment 2 Atin Mukherjee 2017-05-09 07:53:46 UTC 
downstream patch : https://code.engineering.redhat.com/gerrit/102946
Comment 4 Bala Konda Reddy M 2017-05-29 11:12:32 UTC 
Build :3.8.4-18.2

glusterd is not crashing when peering an ip where the ip is more than acceptable range.

[root@dhcp37-98 glusterpackages]# gluster peer probe 10.70.37.259
peer probe: failed: Probe returned with Transport endpoint is not connected

glusterd is not crashing when invalid hostname is given.
root@dhcp37-98 glusterpackages]# gluster peer probe abcd
peer probe: failed: Probe returned with Transport endpoint is not connected

Hence marking the bz as verified
Comment 6 errata-xmlrpc 2017-06-08 09:37:20 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, 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/RHBA-2017:1419