Bug 1449076 - [RHEL6] glusterd crashes when peering an IP where the address is more than acceptable range (>255) OR with random hostnames
Summary: [RHEL6] glusterd crashes when peering an IP where the address is more than ac...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Atin Mukherjee
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On: 1433276 1433578 1434399 1440162
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-09 07:51 UTC by Atin Mukherjee
Modified: 2017-06-08 09:37 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.8.4-18.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1440162
Environment:
Last Closed: 2017-06-08 09:37:20 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1419 0 normal SHIPPED_LIVE glusterfs bug fix update 2017-06-08 13:34:08 UTC

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
Note You need to log in before you can comment on or make changes to this bug.