Bug 1360979 - [SNAPSHOT]: The PID for snapd is displayed even after snapd process is killed.
Summary: [SNAPSHOT]: The PID for snapd is displayed even after snapd process is killed.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: 3.7.13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On: 1358244 1360985
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-28 06:00 UTC by Avra Sengupta
Modified: 2016-09-01 09:33 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.7.15
Clone Of: 1358244
Environment:
Last Closed: 2016-09-01 09:20:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Avra Sengupta 2016-07-28 06:00:33 UTC
+++ This bug was initially created as a clone of Bug #1358244 +++

Description of problem:
Even after snapd process is killed, it's older pid continues to be displayed. 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Vijay Bellur on 2016-07-22 02:14:41 EDT ---

REVIEW: http://review.gluster.org/14981 (snapshot/snapd: Don't dispay pid when snapd is offline) posted (#1) for review on master by Avra Sengupta (asengupt)

--- Additional comment from Vijay Bellur on 2016-07-22 22:45:46 EDT ---

REVIEW: http://review.gluster.org/14981 (snapshot/snapd: Don't display pid when snapd is offline) posted (#2) for review on master by Avra Sengupta (asengupt)

--- Additional comment from Vijay Bellur on 2016-07-26 03:55:22 EDT ---

REVIEW: http://review.gluster.org/14981 (snapshot/snapd: Don't display pid when snapd is offline) posted (#3) for review on master by Avra Sengupta (asengupt)

--- Additional comment from Vijay Bellur on 2016-07-27 18:07:26 EDT ---

COMMIT: http://review.gluster.org/14981 committed in master by Jeff Darcy (jdarcy) 
------
commit ec6925a379c7bee071df1638bc2751b266cee346
Author: Avra Sengupta <asengupt>
Date:   Fri Jul 22 11:40:32 2016 +0530

    snapshot/snapd: Don't display pid when snapd is offline
    
    We were previously reading the pidfile, and displaying
    the pid even if snapd daemon is not running. Now to fix
    it, we re-assign pid value to -1, if snapd is offline.
    
    Change-Id: I4baff8d489fe9380061c52aea006db90fa421cd7
    BUG: 1358244
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/14981
    Tested-by: Vijay Bellur <vbellur>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Jeff Darcy <jdarcy>

Comment 1 Vijay Bellur 2016-07-28 06:10:27 UTC
REVIEW: http://review.gluster.org/15032 (snapshot/snapd: Don't display pid when snapd is offline) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2016-08-02 07:08:27 UTC
REVIEW: http://review.gluster.org/15032 (snapshot/snapd: Don't display pid when snapd is offline) posted (#4) for review on release-3.7 by Avra Sengupta (asengupt)

Comment 3 Worker Ant 2016-08-22 08:34:35 UTC
COMMIT: http://review.gluster.org/15032 committed in release-3.7 by Rajesh Joseph (rjoseph) 
------
commit 888ad44a9da3006b3e5695e5e5b40d6e446aa109
Author: Avra Sengupta <asengupt>
Date:   Fri Jul 22 11:40:32 2016 +0530

    snapshot/snapd: Don't display pid when snapd is offline
    
        Backport of http://review.gluster.org/#/c/14981/
    
    We were previously reading the pidfile, and displaying
    the pid even if snapd daemon is not running. Now to fix
    it, we re-assign pid value to -1, if snapd is offline.
    
    > Reviewed-on: http://review.gluster.org/14981
    > Tested-by: Vijay Bellur <vbellur>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Smoke: Gluster Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > Reviewed-by: Jeff Darcy <jdarcy>
    
    (cherry picked from commit ec6925a379c7bee071df1638bc2751b266cee346)
    
    Change-Id: I4baff8d489fe9380061c52aea006db90fa421cd7
    BUG: 1360979
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/15032
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 4 Kaushal 2016-09-01 09:20:59 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.7.15, please open a new bug report.

glusterfs-3.7.15 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://www.gluster.org/pipermail/gluster-devel/2016-September/050714.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 5 Kaushal 2016-09-01 09:33:03 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.7.15, please open a new bug report.

glusterfs-3.7.15 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://www.gluster.org/pipermail/gluster-devel/2016-September/050714.html
[2] https://www.gluster.org/pipermail/gluster-users/


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