Back to bug 1314391

Who When What Removed Added
SATHEESARAN 2016-03-03 13:42:49 UTC Priority high unspecified
Atin Mukherjee 2016-03-04 06:21:24 UTC Keywords ZStream
Status ASSIGNED POST
CC amukherj
Blocks 1311817
Atin Mukherjee 2016-03-04 06:33:05 UTC Blocks 1311817 1299184
Alok 2016-03-07 09:38:54 UTC CC asrivast
Red Hat Bugzilla Rules Engine 2016-03-08 08:16:01 UTC Target Release --- RHGS 3.1.3
Gaurav Kumar Garg 2016-03-08 09:26:14 UTC Depends On 1315626
Gaurav Kumar Garg 2016-03-08 09:26:47 UTC Depends On 1315626
Rahul Hinduja 2016-03-27 14:46:41 UTC CC rhinduja
QA Contact sasundar bsrirama
Atin Mukherjee 2016-03-28 07:09:09 UTC Status POST MODIFIED
errata-xmlrpc 2016-04-20 11:22:03 UTC Status MODIFIED ON_QA
Satish Mohan 2016-04-20 11:29:32 UTC Fixed In Version glusterfs-3.7.9-2
Byreddy 2016-04-27 05:18:45 UTC Status ON_QA VERIFIED
Gaurav Kumar Garg 2016-05-04 10:13:45 UTC Doc Text If a node N1 and node N2 is part of the cluster and a node N2 try to reprobe node N1 when N1 is disconnected by any means (for eg: either server is down or glusterd is not running or there is a network outage, or firewall is
blocking port number 24007 on which glusterd listen, etc.), then glusterd trying to send back two responses to CLI resulting into a double free and a glusterd crash.

glusterd was crashing only when user has done first peer probe with hostname and re-probe with ip-address or vice-versa.

With this fix glusterd will send response to cli only once and prevent glusterd crash.
John Skeoch 2016-06-05 23:39:21 UTC CC ggarg smohan
John Skeoch 2016-06-05 23:41:05 UTC Assignee ggarg smohan
Laura Bailey 2016-06-09 03:21:14 UTC Doc Text If a node N1 and node N2 is part of the cluster and a node N2 try to reprobe node N1 when N1 is disconnected by any means (for eg: either server is down or glusterd is not running or there is a network outage, or firewall is
blocking port number 24007 on which glusterd listen, etc.), then glusterd trying to send back two responses to CLI resulting into a double free and a glusterd crash.

glusterd was crashing only when user has done first peer probe with hostname and re-probe with ip-address or vice-versa.

With this fix glusterd will send response to cli only once and prevent glusterd crash.
When a node was disconnected from a cluster, and a peer probe was sent to that node using an IP address when initial peering was done with hostname, or vice versa, glusterd attempted to return two responses (one for the IP address, one for the hostname), which resulted in a glusterd crash. This has been corrected so that only one response is sent, preventing the crash.
Flags needinfo?(amukherj)
Atin Mukherjee 2016-06-09 04:37:23 UTC Flags needinfo?(amukherj)
errata-xmlrpc 2016-06-23 00:49:10 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:10:17 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:10:17 UTC
Rejy M Cyriac 2016-09-17 16:34:13 UTC Sub Component glusterd
Component glusterd glusterd-transition
Rejy M Cyriac 2016-09-17 16:47:19 UTC CC rhs-bugs, storage-qa-internal, vbellur
Component glusterd-transition glusterd

Back to bug 1314391