Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1109812

Summary:	glusterd crash when detaching a node from existing cluster with peer detach command
Product:	[Community] GlusterFS	Reporter:	krishnan parthasarathi <kparthas>
Component:	glusterd	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	bugs, gluster-bugs, nsathyan, rcyriac, saujain, ssamanta
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1108570	Environment:
Last Closed:	2014-11-11 08:35:12 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:	1108570
Bug Blocks:

Description krishnan parthasarathi 2014-06-16 12:14:02 UTC

glusterd crashes when a peer detach (2 or more) is executed in quick succession when the peer being detached is not responding.

Steps to reproduce:
1) Create a cluster of 2 or more nodes.
2) Using iptables block replies from one of the nodes (say A).
3) gluster peer detach A (repeat 2 times)
glusterd will crash.

Comment 1 Anand Avati 2014-06-16 12:15:20 UTC

REVIEW: http://review.gluster.org/8079 (glusterd: Fail peer probe/detach commands when peer detach is ongoing) posted (#1) for review on master by Krishnan Parthasarathi (kparthas)

Comment 2 Anand Avati 2014-06-16 17:03:20 UTC

COMMIT: http://review.gluster.org/8079 committed in master by Vijay Bellur (vbellur) 
------
commit 6e33d855815726bd8ebf1c7cdc3cf233ff7ac231
Author: Krishnan Parthasarathi <kparthas>
Date:   Mon Jun 16 17:39:08 2014 +0530

    glusterd: Fail peer probe/detach commands when peer detach is ongoing
    
    Change-Id: Ifd8099bc235eb395e8fd9ead3197bef71c78042b
    BUG: 1109812
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/8079
    Reviewed-by: Atin Mukherjee <amukherj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-09-22 12:43:02 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:35:12 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users