Bug 1286601
Summary: | vol quota enable fails when transport.socket.bind-address is set in glusterd | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Mohamed Ashiq <mliyazud> |
Component: | quota | Assignee: | Mohamed Ashiq <mliyazud> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.6 | CC: | bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1277105 | Environment: | |
Last Closed: | 2016-04-19 07:49:29 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: | 1277105, 1286605 | ||
Bug Blocks: |
Description
Mohamed Ashiq
2015-11-30 10:05:22 UTC
REVIEW: http://review.gluster.org/12819 (quota: vol quota fails when transport.socket.bind-address is set in glusterd) posted (#1) for review on release-3.7 by Mohamed Ashiq Liyazudeen (mliyazud) REVIEW: http://review.gluster.org/12819 (quota: vol quota fails when transport.socket.bind-address is set in glusterd) posted (#2) for review on release-3.7 by Mohamed Ashiq Liyazudeen (mliyazud) COMMIT: http://review.gluster.org/12819 committed in release-3.7 by Atin Mukherjee (amukherj) ------ commit e1a9914fb318cbdd2bb8f36881e8f5f0b45ce76c Author: Mohamed Ashiq <mliyazud> Date: Mon Nov 9 22:09:34 2015 +0530 quota: vol quota fails when transport.socket.bind-address is set in glusterd When glusterd is binded to specific IP quota fails, since the server is hardcoded to localhost. IP can be assigned in the glusterd part of quota, but IP is not populated in cli part. So Quota makes use of glusterfsd's unix domain socket transport type. Signed-off-by: Mohamed Ashiq <mliyazud> Signed-off-by: Humble Devassy Chirammal <hchiramm> >Change-Id: Ib03332cc203795456ee6087017cea08eed3d7417 >BUG: 1277105 >Signed-off-by: Mohamed Ashiq <mliyazud> >Signed-off-by: Humble Devassy Chirammal <hchiramm> >Reviewed-on: http://review.gluster.org/12489 >Reviewed-by: Manikandan Selvaganesh <mselvaga> >Tested-by: NetBSD Build System <jenkins.org> >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Vijaikumar Mallikarjuna <vmallika> Reviewed-by: Atin Mukherjee <amukherj> Change-Id: I0fb2b5aff664101135c4f40d47517c1b1759b0af BUG: 1286601 Reviewed-on: http://review.gluster.org/12819 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijaikumar Mallikarjuna <vmallika> 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.7, please open a new bug report. glusterfs-3.7.7 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-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |