Bug 1285168
Summary: | vol heal info fails when transport.socket.bind-address is set in glusterd | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Mohamed Ashiq <mliyazud> |
Component: | replicate | Assignee: | Mohamed Ashiq <mliyazud> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.6 | CC: | bugs, hchiramm, hgowtham, pcuzner, sankarshan, storage-qa-internal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1277997 | Environment: | |
Last Closed: | 2016-04-19 07:49:12 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: | 1257343, 1277997, 1285962 | ||
Bug Blocks: |
Comment 1
Vijay Bellur
2015-11-27 06:02:32 UTC
*** Bug 1285962 has been marked as a duplicate of this bug. *** REVIEW: http://review.gluster.org/12772 (afr:vol heal info 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/12772 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 4754ae1f612e5acdd56852dfebbf1afec1dac2f2 Author: Mohamed Ashiq <mliyazud> Date: Thu Nov 5 20:22:02 2015 +0530 afr:vol heal info fails when transport.socket.bind-address is set in glusterd Problem: If glusterd's bind address is specified using transport.socket.bind- address option to a specific IP, the heal command 'gluster volume heal <VOLNAME> info' fails with error '<vol_name>: Not able to fetch volfile from glusterd.Volume heal failed.' This patch uses Unix domain socket transport type of libglfapi to get the volfile. Signed-off-by: Mohamed Ashiq <mliyazud> Signed-off-by: Humble Devassy Chirammal <hchiramm> >Change-Id: Ic4239b339f0246d77f1622c07d5f4708129d30c7 >BUG: 1277997 >Signed-off-by: Mohamed Ashiq <mliyazud> >Signed-off-by: Humble Devassy Chirammal <hchiramm> >Reviewed-on: http://review.gluster.org/12508 >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Ravishankar N <ravishankar> >Tested-by: NetBSD Build System <jenkins.org> >Reviewed-by: Niels de Vos <ndevos> >Reviewed-by: Anuradha Talur <atalur> >Reviewed-by: Pranith Kumar Karampuri <pkarampu> Change-Id: I8f88134125acac7a02318c112fc055271edeca2f BUG: 1285168 Reviewed-on: http://review.gluster.org/12772 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Pranith Kumar Karampuri <pkarampu> 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 |