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

Bug 1646869

Summary:	gNFS crashed when processing "gluster v status [vol] nfs clients"
Product:	[Community] GlusterFS	Reporter:	hujianfei <jefferymymy>
Component:	nfs	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-25 16:31:51 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 hujianfei 2018-11-06 08:07:49 UTC

Description of problem:
when processing "gluster v status [vol] nfs clients" after "systemctl restart glusterd", gnfs will crash with certain probability.

dump trace info:
/lib64/libglusterfs.so.0(+0x270f0)[0x7effb6c7b0f0]
/lib64/libglusterfs.so.0(gf_print_trace+0x334)[0x7effb6c854a4]
/lib64/libc.so.6(+0x35270)[0x7effb52e7270]
/usr/sbin/glusterfs(glusterfs_handle_node_status+0x155)[0x7effb7196905]
/lib64/libglusterfs.so.0(+0x63f40)[0x7effb6cb7f40]
/lib64/libc.so.6(+0x46d40)[0x7effb52f8d40]

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


How reproducible:

certain probability

Steps to Reproduce:
1. create replicate volume naming rep
2. set rep volume nfs.disable off
3. process cli: "systemctl restart glusterd; gluster volume status rep nfs clients"

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-11-06 12:05:54 UTC

REVIEW: https://review.gluster.org/21569 (glusterfsd: Do not process GLUSTERD_NODE_STATUS if graph is not ready) posted (#1) for review on master by Hu Jianfei

Comment 2 Worker Ant 2018-11-08 02:41:45 UTC

REVIEW: https://review.gluster.org/21569 (glusterfsd: Do not process GLUSTERD_NODE_STATUS if graph is not ready) posted (#4) for review on master by Amar Tumballi

Comment 3 Shyamsundar 2019-03-25 16:31:51 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/