Bug 1277997 - vol heal info fails when transport.socket.bind-address is set in glusterd
Summary: vol heal info fails when transport.socket.bind-address is set in glusterd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Mohamed Ashiq
QA Contact:
URL:
Whiteboard:
Depends On: 1257343
Blocks: 1285168 1285962
TreeView+ depends on / blocked
 
Reported: 2015-11-04 14:08 UTC by Mohamed Ashiq
Modified: 2016-06-16 13:42 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1257343
: 1285168 1285962 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:42:46 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Mohamed Ashiq 2015-11-06 13:59:30 UTC
patch :

http://review.gluster.org/12508

Comment 2 Vijay Bellur 2015-11-18 03:43:49 UTC
REVIEW: http://review.gluster.org/12508 (afr:vol heal info fails when transport.socket.bind-address is set in glusterd) posted (#8) for review on master by Mohamed Ashiq Liyazudeen (mliyazud)

Comment 3 Vijay Bellur 2015-11-24 05:44:30 UTC
COMMIT: http://review.gluster.org/12508 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 31f0fd1d401f1a4c007fd44854f99f15aff2346b
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.
    
    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>

Comment 4 Niels de Vos 2016-06-16 13:42:46 UTC
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


Note You need to log in before you can comment on or make changes to this bug.