[Bugs] [Bug 1277105] New: vol quota enable fails when transport.socket.bind-address is set in glusterd

[bugzilla at redhat.com]

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

            Bug ID: 1277105
           Summary: vol quota enable fails when
                    transport.socket.bind-address is set in glusterd
           Product: GlusterFS
           Version: mainline
         Component: quota
          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.issue 'gluster volume quota <VOLNAME> enable'

Actual results:
command fails with error "quota: Could not start quota auxiliary mount"

Expected results:
quota should create auxiliary mount and should be enabled even
'transport.socket.bind-address' is set. 

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.