Bug 1288085

Summary:	glusterd related core observed while probing a node which is already in cluster.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Shashank Raj <sraj>
Component:	glusterd	Assignee:	Gaurav Kumar Garg <ggarg>
Status:	CLOSED WORKSFORME	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhgs-3.1	CC:	amukherj, ggarg, nlevinki, sashinde, sasundar, smohan, sraj, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	glusterd
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-11 18:04:29 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:

Description Shashank Raj 2015-12-03 13:08:14 UTC

Description of problem:

glusterd related core observed while probing a node which is already in cluster.

Version-Release number of selected component (if applicable):

glusterfs-3.7.5-8

How reproducible:


Steps to Reproduce:
1.While running automated cases related to snapshots observed core related to glusterd.
2.This happened while probing a node which is already a part of the cluster.

Actual results:

glusterd related core observed

Expected results:


Additional info:

Comment 2 Shashank Raj 2015-12-03 13:19:53 UTC

sos reports are at http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1288085

Comment 3 Gaurav Kumar Garg 2015-12-07 08:52:02 UTC

Hi shashank,

core file is missing from the sos report. could you check it again and attach core file somewhere so can we can analyse this issue. we need core file to analyse this issue.

Comment 4 Shashank Raj 2015-12-07 09:25:34 UTC

core file is placed at http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1288085/core/core.4750

Comment 5 Gaurav Kumar Garg 2015-12-09 07:09:43 UTC

Hi Shashank,

Its very rare to reproduce this issue. glusterd crashed because at the time of sending response to CLI some application have corrupted dictionary data. by looking into backtrace using gdb we didn't found out much information regarding this which application have corrupted dictionary and freed its one of the member which is trying to free again.

Comment 6 Atin Mukherjee 2015-12-11 04:15:30 UTC

Lowering both priority and severity as the crash is not reproducible.

Comment 7 Atin Mukherjee 2016-02-11 18:04:29 UTC

Shashank,

Since this bug is not reproducible and we haven't heard any such core in recent times closing this bug. Feel free to reopen if you hit it again.