Bug 1315666
| Summary: | Data Tiering:tier volume status shows as in-progress on all nodes of a cluster even if the node is not part of volume | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | hari gowtham <hgowtham> | |
| Component: | tiering | Assignee: | hari gowtham <hgowtham> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> | |
| Severity: | low | Docs Contact: | ||
| Priority: | high | |||
| Version: | mainline | CC: | asrivast, bugs, dlambrig, josferna, nchilaka, rhinduja, rkavunga, sankarshan, smohan | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1283957 | |||
| : | 1316808 1347509 (view as bug list) | Environment: | ||
| Last Closed: | 2016-06-16 13:59:45 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: | 1283957 | |||
| Bug Blocks: | 1268895, 1316808, 1347509 | |||
|
Comment 1
Vijay Bellur
2016-03-08 11:56:48 UTC
REVIEW: http://review.gluster.org/13647 (Tier: displaying status only one the nodes running tierd) posted (#2) for review on master by hari gowtham (hari.gowtham005) COMMIT: http://review.gluster.org/13647 committed in master by Dan Lambright (dlambrig) ------ commit 537822d7eb7732f2f65300668355b6d7db448f39 Author: hari gowtham <hgowtham> Date: Tue Mar 8 17:22:35 2016 +0530 Tier: displaying status only one the nodes running tierd When tier status is given on a cluster where one node doesn't have tierd running, the status is shown as not started. The status of the node without tierd should not be displayed. This patch will skip if the current node if the status is not started Change-Id: Ibeb39f13133f94a5869b020c5ccd9bd6992323f1 BUG: 1315666 Signed-off-by: hari gowtham <hgowtham> Reviewed-on: http://review.gluster.org/13647 Smoke: Gluster Build System <jenkins.com> Tested-by: hari gowtham <hari.gowtham005> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started during volume restart and tier start force on the nodes where tierd is not supposed to run.) posted (#1) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#2) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#3) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#4) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#5) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#6) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#7) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#8) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#9) for review on master by hari gowtham (hari.gowtham005) REVIEW: http://review.gluster.org/14106 (Tier/glusterd: Resetting the tier status value to not started) posted (#10) for review on master by hari gowtham (hari.gowtham005) COMMIT: http://review.gluster.org/14106 committed in master by Atin Mukherjee (amukherj) ------ commit 3f07e9324d8fa62a6231f387270d8e7559ac71e0 Author: hari <hgowtham> Date: Thu Apr 28 19:36:25 2016 +0530 Tier/glusterd: Resetting the tier status value to not started Problem: during a volume restart or tier start force, the value of tier status is set as started irrespective of the result. Fix: The appropriate value of status is set during the restart of rebalance function. Change-Id: I6164f0add48542a57dee059e80fa0f9bb036dbef BUG: 1315666 Signed-off-by: hari <hgowtham> Reviewed-on: http://review.gluster.org/14106 Tested-by: mohammed rafi kc <rkavunga> Tested-by: hari gowtham <hari.gowtham005> Smoke: Gluster Build System <jenkins.com> Reviewed-by: mohammed rafi kc <rkavunga> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> 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.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 |