Bug 1161015
| Summary: | [USS]: snapd process is not killed once the glusterd comes back | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sachin Pandit <spandit> | |
| Component: | glusterd | Assignee: | Sachin Pandit <spandit> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | asengupt, bugs, gluster-bugs, nsathyan, rhinduja, storage-qa-internal | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | USS | |||
| Fixed In Version: | glusterfs-3.7.0 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1158883 | |||
| : | 1175735 (view as bug list) | Environment: | ||
| Last Closed: | 2015-05-14 17:28:20 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: | 1158883, 1240338, 1240952, 1240955 | |||
| Bug Blocks: | 1175735 | |||
|
Comment 1
Anand Avati
2014-11-06 13:37:13 UTC
REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled.) posted (#2) for review on master by Sachin Pandit (spandit) REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled) posted (#3) for review on master by Sachin Pandit (spandit) REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled) posted (#4) for review on master by Sachin Pandit (spandit) REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled) posted (#5) for review on master by Sachin Pandit (spandit) REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled) posted (#6) for review on master by Sachin Pandit (spandit) REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled) posted (#7) for review on master by Sachin Pandit (spandit) REVIEW: http://review.gluster.org/9062 (USS : Kill snapd during glusterd restart if USS is disabled) posted (#8) for review on master by Sachin Pandit (spandit) COMMIT: http://review.gluster.org/9062 committed in master by Krishnan Parthasarathi (kparthas) ------ commit a7ec009499f2c8f0c96aa03110ff4755eef8f1b8 Author: Sachin Pandit <spandit> Date: Wed Nov 5 11:09:59 2014 +0530 USS : Kill snapd during glusterd restart if USS is disabled Problem : When glusterd is down on one of the nodes and during that time if USS is disabled then snapd will still be running in the node where glusterd was down. Solution : during restart of glusterd check if USS is disabled, if so then issue a kill for snapd. NOTE : The test case which I wrote in my previous patchset is facing some spurious failures, hence I thought of removing that test case. I'll add the test case once the issue is resolved. Change-Id: I2870ebb4b257d863cdfc319e8485b19e932576e9 BUG: 1161015 Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/9062 Reviewed-by: Rajesh Joseph <rjoseph> Reviewed-by: Avra Sengupta <asengupt> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas> 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |