Bug 1219850

Summary:	Data Tiering: attaching a tier with non supported replica count crashes glusterd on local host
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.7.0	CC:	bugs, dlambrig, josferna, nchilaka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1215122	Environment:
Last Closed:	2015-05-15 17:09:52 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:	1215122
Bug Blocks:	1186580, 1221957, 1229269, 1260923, 1273726, 1274411

Description Mohammed Rafi KC 2015-05-08 13:19:10 UTC

+++ This bug was initially created as a clone of Bug #1215122 +++

Description of problem:
======================
I tried to attach a tier with replica count as 10 with one brick and this caused the glusterd to crash 

gluster v info
Connection failed. Please check if gluster daemon is operational.

[2015-04-24 10:42:12.496850] I [glusterd-brick-ops.c:1104:glusterd_op_perform_add_bricks] 0-management: replica-count is set 10
[2015-04-24 10:42:12.496869] I [glusterd-brick-ops.c:1108:glusterd_op_perform_add_bricks] 0-management: type is set 5, need to change it
The message "I [MSGID: 106006] [glusterd-svc-mgmt.c:327:glusterd_svc_common_rpc_notify] 0-management: quotad has disconnected from glusterd." repeated 34 times between [2015-04-24 10:40:28.174251] and [2015-04-24 10:42:10.199015]
The message "I [MSGID: 106006] [glusterd-snapd-svc.c:379:glusterd_snapdsvc_rpc_notify] 0-management: snapd has disconnected from glusterd." repeated 139 times between [2015-04-24 10:40:28.174200] and [2015-04-24 10:42:11.199308]
pending frames:
frame : type(0) op(0)
patchset: git://git.gluster.com/glusterfs.git
signal received: 11
time of crash: 
2015-04-24 10:42:12
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.7dev
/lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0xb2)[0x7f522509ffa2]
/lib64/libglusterfs.so.0(gf_print_trace+0x32d)[0x7f52250b80cd]
/lib64/libc.so.6(+0x35650)[0x7f5223a94650]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x9468c)[0x7f5219ed468c]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x99d35)[0x7f5219ed9d35]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x9a00b)[0x7f5219eda00b]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x93c12)[0x7f5219ed3c12]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x941f4)[0x7f5219ed41f4]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(generate_client_volfiles+0x12a)[0x7f5219edbb4a]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_create_volfiles+0x29)[0x7f5219edc8c9]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_create_volfiles_and_notify_services+0x1b)[0x7f5219edc97b]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_perform_add_bricks+0x63f)[0x7f5219f06cef]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_add_brick+0x1cf)[0x7f5219f089df]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_commit_perform+0x6b3)[0x7f5219e98813]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(gd_commit_op_phase+0xb6)[0x7f5219f0e416]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(gd_sync_task_begin+0x749)[0x7f5219f0f719]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_begin_synctask+0x2c)[0x7f5219f0f78c]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(__glusterd_handle_add_brick+0x4e5)[0x7f5219f057b5]
/usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x30)[0x7f5219e861f0]
/lib64/libglusterfs.so.0(synctask_wrap+0x12)[0x7f52250da182]
/lib64/libc.so.6(+0x470f0)[0x7f5223aa60f0]
---------


Version-Release number of selected component (if applicable):
============================================================
glusterfs 3.7dev built on Apr 17 2015 14:27:16
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.

glusterfs-api-3.7dev-0.1009.git8b987be.el7.centos.x86_64
glusterfs-cli-3.7dev-0.1009.git8b987be.el7.centos.x86_64
glusterfs-3.7dev-0.1009.git8b987be.el7.centos.x86_64
glusterfs-server-3.7dev-0.1009.git8b987be.el7.centos.x86_64
glusterfs-fuse-3.7dev-0.1009.git8b987be.el7.centos.x86_64
glusterfs-libs-3.7dev-0.1009.git8b987be.el7.centos.x86_64



Steps to Reproduce:
==================
1.have a multinode gluster
2.create a dist-rep volume
3.attach a tier with replica as 10 and one brick 


Actual results:
=================
glusterd crashes

Expected results:
===============
proper error msg should be thrown, if replica or bricks count are not correct

--- Additional comment from nchilaka on 2015-04-24 07:20:25 EDT ---

sosreports 
rhsqe-repo sosreports]# /home/repo/sosreports/1215122

--- Additional comment from Anand Avati on 2015-04-28 09:52:38 EDT ---

REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-28 10:00:42 EDT ---

REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-29 09:14:15 EDT ---

REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#3) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-30 02:15:26 EDT ---

REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#4) for review on master by mohammed rafi  kc (rkavunga)

Comment 1 Anand Avati 2015-05-08 14:31:55 UTC

REVIEW: http://review.gluster.org/10681 (tiering/cli: Check replica count and bricks are proper or not) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Anand Avati 2015-05-09 20:46:31 UTC

REVIEW: http://review.gluster.org/10710 (tiering/cli: Check replica count and bricks are proper or not) posted (#2) for review on release-3.7 by Niels de Vos (ndevos)

Comment 3 Niels de Vos 2015-05-15 17:09:52 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user