Bug 1253165
| Summary: | glusterd services are not handled properly when re configuring services | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Anand Nekkunti <anekkunt> |
| Component: | glusterd | Assignee: | Anand Nekkunti <anekkunt> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.7.3 | CC: | anekkunt, asengupt, bugs, gluster-bugs, nsathyan, rkavunga |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.4 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1209329 | Environment: | |
| Last Closed: | 2015-09-09 09:39:37 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: | 1209329 | ||
| Bug Blocks: | 1221869, 1230532 | ||
|
Description
Anand Nekkunti
2015-08-13 07:21:07 UTC
Patch present at http://review.gluster.org/#/c/11905/ COMMIT: http://review.gluster.org/11905 committed in release-3.7 by Atin Mukherjee (amukherj) ------ commit c49b8064bd83a512dd962d4c4168728886ff0a5c Author: anand <anekkunt> Date: Wed May 20 19:52:11 2015 +0530 glusterd: Stop/restart/notify to daemons(svcs) during reset/set on a volume problem : Reset/set commands were not working properly. reset command returns success but it not sending notification to svcs if corresponding graph modified. Fix: Whenever reset/set command issued, generate the temp graph and compare with original graph and do the fallowing actions 1.) If both graph are identical nothing to do with svcs. 2.) If any changes in graph topology restart/stop service by calling svc manager. 3) If changes in options send notify signal by calling glusterd_fetchspec_notify. Back port of: >Change-Id: I852c4602eafed1ae6e6a02424814fe3a83e3d4c7 >BUG: 1209329 >Signed-off-by: anand <anekkunt> >Reviewed-on: http://review.gluster.org/10850 >Tested-by: NetBSD Build System <jenkins.org> >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Atin Mukherjee <amukherj> >(cherry picked from commit 7255febab2c38cc89b71f2519a20d10f53586000) Change-Id: I42aa757ecc6b5b307b5927d11f12d08f57ac0ae2 BUG: 1253165 Reviewed-on: http://review.gluster.org/11905 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> 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.4, please open a new bug report. glusterfs-3.7.4 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/12496 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |