Bug 1252448

Summary:	Probing a new node, which is part of another cluster, should throw proper error message in logs and CLI
Product:	[Community] GlusterFS	Reporter:	Gaurav Kumar Garg <ggarg>
Component:	glusterd	Assignee:	Satish Mohan <smohan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, mlawrenc, nlevinki, sasundar, smohan, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	glusterd
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1237022
Clones:	1317861 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:30:53 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:	1004699, 1237022
Bug Blocks:	1010153, 1216951, 1317861

Comment 1 Anand Avati 2015-08-11 13:04:43 UTC

REVIEW: http://review.gluster.org/11884 (glusterd: probing a new node, which is part of another cluster should give error) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)

Comment 2 Anand Avati 2015-08-29 03:44:20 UTC

COMMIT: http://review.gluster.org/11884 committed in master by Atin Mukherjee (amukherj) 
------
commit 31a36dca20a976b143cc5c970e115d8d36df847a
Author: Gaurav Kumar Garg <garg.gaurav52>
Date:   Tue Aug 11 18:17:31 2015 +0530

    glusterd: probing a new node, which is part of another cluster should give error
    
    If user try to add node to extant cluster using "gluster peer probe \
    <ip/hostname>" command then command is failing but its not giving
    proper cause of failure.
    
    This fix will take control of proper error message during peer probe
    with already extant cluster.
    
    Change-Id: I4f993e78c0e1b3e061153b984ec5e9b70085aef5
    BUG: 1252448
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    Reviewed-on: http://review.gluster.org/11884
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 5 Niels de Vos 2016-06-16 13:30:53 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.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user