Bug 762935 (GLUSTER-1203)

Summary:	glusterfs returns 0 even if it fails
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	core	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raghavendra Bhat <rabhat>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	3.1-alpha	CC:	amarts, craig, gluster-bugs, gluster, jdarcy, nsathyan, pavan, sac, tejas, vijay, vikas
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:53:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raghavendra Bhat 2010-07-22 12:05:42 UTC

Suppose a server process of glusterfs is started and using the same volfile if another server is executed it should fail returning a non zero value. But it is returning a zero. Thus applications which use glusterfs such as glusterd, cli may cause some errors due to this behavior.

Comment 1 Pavan Vilas Sondur 2010-08-04 13:55:23 UTC

*** Bug 1284 has been marked as a duplicate of this bug. ***

Comment 2 Vijay Bellur 2010-10-28 14:32:30 UTC

*** Bug 2016 has been marked as a duplicate of this bug. ***

Comment 3 Amar Tumballi 2011-04-25 09:33:15 UTC

Please update the status of this bug as its been more than 6months since its filed (bug id < 2000)

Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.

Comment 4 Amar Tumballi 2011-07-05 01:29:24 UTC

*** Bug 2295 has been marked as a duplicate of this bug. ***

Comment 5 Amar Tumballi 2011-07-05 01:39:05 UTC

*** Bug 3085 has been marked as a duplicate of this bug. ***

Comment 6 Amar Tumballi 2011-07-15 05:38:29 UTC

*** Bug 2955 has been marked as a duplicate of this bug. ***

Comment 7 Amar Tumballi 2011-09-27 05:49:57 UTC

Planing to keep 3.4.x branch as "internal enhancements" release without any features. So moving these bugs to 3.4.0 target milestone.

Comment 8 Anand Avati 2012-01-26 13:23:38 UTC

CHANGE: http://review.gluster.com/2694 (protocol/client: Pass the right arguments to CLIENT_GET_REMOTE_FD) merged in master by Anand Avati (avati)

Comment 9 Anand Avati 2012-03-21 18:58:19 UTC

CHANGE: http://review.gluster.com/479 (glusterd: bring in feature to use syncop for mgmt ops) merged in master by Anand Avati (avati)

Comment 10 Anand Avati 2012-03-21 18:58:37 UTC

CHANGE: http://review.gluster.com/579 (core: enable process to return the appropriate error code) merged in master by Anand Avati (avati)

Comment 11 Amar Tumballi 2012-07-11 06:05:03 UTC

*** Bug 837817 has been marked as a duplicate of this bug. ***

Comment 12 Vijay Bellur 2012-08-21 03:41:25 UTC

CHANGE: http://review.gluster.org/3832 (rpcsvc: remove .vector_actor and related changes) merged in master by Vijay Bellur (vbellur)

Comment 13 Sachidananda Urs 2012-12-19 07:49:04 UTC

Firstly with the current usage this scenario does not arise. Since we no longer write glusterfs volume files by hand. And no longer start the gluster process by hand, but instead use the cli.

To test this, create a volume, and use the generated volume file to start glusterfsd by hand using the command line:

glusterfsd -f <vol-filename>

This will start the glusterfsd process. Now try to start glusterfsd process again, by using the same command and the same volume file. glusterfsd should fail with non-zero return status.