Bug 1360979
Summary: | [SNAPSHOT]: The PID for snapd is displayed even after snapd process is killed. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Avra Sengupta <asengupt> |
Component: | snapshot | Assignee: | Avra Sengupta <asengupt> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.13 | CC: | bugs, rjoseph |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.15 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1358244 | Environment: | |
Last Closed: | 2016-09-01 09:20:59 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: | |||
Bug Depends On: | 1358244, 1360985 | ||
Bug Blocks: |
Description
Avra Sengupta
2016-07-28 06:00:33 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) 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) 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> 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/ 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/ |