Bug 1331042 - glusterfsd: return actual exit status on mount process
Summary: glusterfsd: return actual exit status on mount process
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Prasanna Kumar Kalever
QA Contact:
URL:
Whiteboard:
: 1335731 (view as bug list)
Depends On:
Blocks: 1331938 1335731
TreeView+ depends on / blocked
 
Reported: 2016-04-27 14:07 UTC by Prasanna Kumar Kalever
Modified: 2016-06-16 14:04 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of:
: 1331938 1335731 (view as bug list)
Environment:
Last Closed: 2016-06-16 14:04:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Prasanna Kumar Kalever 2016-04-27 14:07:52 UTC
Description of problem:
Currently, we always exit mount process with the pid as the exit number
which is return value of the waitpid(), it is not the exit value of the
child process

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

Expected results:
exit with actual status/code

Comment 1 Vijay Bellur 2016-04-27 14:10:06 UTC
REVIEW: http://review.gluster.org/14094 (glusterfsd: fix to return actual exit status on mount process) posted (#1) for review on master by Prasanna Kumar Kalever (pkalever)

Comment 2 Vijay Bellur 2016-04-29 13:24:02 UTC
COMMIT: http://review.gluster.org/14094 committed in master by Jeff Darcy (jdarcy) 
------
commit 36d025ef6f178ce5d8c6f7fa09e1cf236976b5ea
Author: Prasanna Kumar Kalever <prasanna.kalever>
Date:   Wed Apr 27 19:29:09 2016 +0530

    glusterfsd: fix to return actual exit status on mount process
    
    Problem:
    Currently, we always exit mount process with the pid as the exit number
    which is return value of the waitpid(), it is not the exit value of the
    child process
    
    Solution:
    Extract the actual exit code/status in case if the child terminated normally,
    that is, by calling exit(3) or _exit(2), or by returning from main()
    
    Change-Id: Iefec6e27b5a5a98a22f016e49967978853662e37
    BUG: 1331042
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever>
    Reviewed-on: http://review.gluster.org/14094
    Tested-by: Prasanna Kumar Kalever <pkalever>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Talur <rtalur>
    Reviewed-by: Jeff Darcy <jdarcy>

Comment 3 Prasanna Kumar Kalever 2016-05-13 06:56:26 UTC
*** Bug 1335731 has been marked as a duplicate of this bug. ***

Comment 4 Niels de Vos 2016-06-16 14:04:45 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.