Bug 1622422

Summary:	glusterd cli is showing brick status N/A even brick is consumed by a brick process
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	glusterd	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:18:02 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 Mohit Agrawal 2018-08-27 07:40:28 UTC

Description of problem:

In CNS environment "gluster v status" is showing brick status N/A even brick is consumed by a brick process.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
"gluster v status" is showing brick status N/A

Expected results:
"gluster v status" should show pid if brick is running.

Additional info:

Comment 1 Mohit Agrawal 2018-08-27 07:45:03 UTC

RCA: glusterd is showing brick status N/A because of no pidfile available for
     the brick.pidfile was cleaned by glusterd_brick_start if the brick was not 
     come up even glusterd_brick_start was calling with only_connect 
     flag value is TRUE.To resolve the same update code of glusterd_brick_start
     pidfile needs to be cleanup only while connect_flag is false.


Posted a patch on upstream https://review.gluster.org/#/c/glusterfs/+/21007/


Thanks
Mohit Agrawal

Comment 2 Worker Ant 2018-08-27 07:47:39 UTC

REVIEW: https://review.gluster.org/21007 (glusterd: glusterd_brick_start shouldn't cleanup pidfile if only_connect           is true) posted (#2) for review on master by MOHIT AGRAWAL

Comment 3 Worker Ant 2018-08-27 11:37:56 UTC

COMMIT: https://review.gluster.org/21007 committed in master by "Atin Mukherjee" <amukherj> with a commit message- glusterd: glusterd_brick_start shouldn't cleanup pidfile if only_connect is true

Problem: Sometime glusterd cleanup pidfile even brick is started
         and cli shows volume status "N/A"

Solution: Update the condition in glusterd_brick_start to avoid
          pidfile cleanup in case if only_connect flag is true

Fixes: bz#1622422
Change-Id: I8decb34597126b848e3a44d957e138833dd97350
Signed-off-by: Mohit Agrawal <moagrawal>

Comment 4 Shyamsundar 2018-10-23 15:18:02 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-5.0, please open a new bug report.

glusterfs-5.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/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/