[Bugs] [Bug 1276386] New: vol replace-brick fails when transport.socket.bind-address is set in glusterd

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1276386

            Bug ID: 1276386
           Summary: vol replace-brick fails when
                    transport.socket.bind-address is set in glusterd
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: mliyazud at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
When you bind glusterd to a specific IP, shd operates correctly but the 'vol
replace-brick' command attempts to contact glusterd on 127.0.0.1 and fails.

Version-Release number of selected component (if applicable):
glusterfs 3.7.x (and prior releases?)

How reproducible:
Every time! I noticed this in a test environment I'm using for containers,
where I bind glusterd host IP.

Steps to Reproduce:
1. use transport.socket.bind-address to bind glusterd to a specific IP on each
host
2.volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> {commit force}

Actual results:
[2015-10-29 13:32:05.603754] I [MSGID: 100030] [glusterfsd.c:2313:main]
0-/usr/local/sbin/glusterfs: Started running /usr/local/sbin/glusterfs version
3.8dev (args: /usr/local/sbin/glusterfs -s localhost --volfile-id test
--client-pid -6 -l /var/log/glusterfs/test-replace-brick-mount.log
/tmp/mntqxzdJu)
[2015-10-29 13:32:05.641149] I [MSGID: 101190]
[event-epoll.c:627:event_dispatch_epoll_worker] 0-epoll: Started thread with
index 1
[2015-10-29 13:32:05.641269] E [socket.c:2274:socket_connect_finish]
0-glusterfs: connection to 127.0.0.1:24007 failed (Connection refused)
[2015-10-29 13:32:05.641325] E [glusterfsd-mgmt.c:1814:mgmt_rpc_notify]
0-glusterfsd-mgmt: failed to connect with remote-host: localhost (Transport
endpoint is not connected)
[2015-10-29 13:32:05.641351] I [glusterfsd-mgmt.c:1820:mgmt_rpc_notify]
0-glusterfsd-mgmt: Exhausted all volfile servers
[2015-10-29 13:32:05.641800] W [glusterfsd.c:1231:cleanup_and_exit]
(-->/usr/local/lib/libgfrpc.so.0(rpc_clnt_notify+0xd2) [0x7fca20149af2]
-->/usr/local/sbin/glusterfs() [0x40cd5f]
-->/usr/local/sbin/glusterfs(cleanup_and_exit+0x4d) [0x407ddd] ) 0-: received
signum (1), shutting down
[2015-10-29 13:32:05.641869] I [fuse-bridge.c:5686:fini] 0-fuse: Unmounting
'/tmp/mntqxzdJu'.


Expected results:
vol replace-brick should work whether glusterd is bound to a specific IP or not

Additional info:
The issue has been discussed with Ravi (ravishankar at redhat.com) and Humble
(hchiramm at redhat.com) and identified as localhost being hardcoded.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.