'transport.socket.bind-address' is not taking effect when starting vol

[zhangxyue]

Description of problem:
I want the vol created with out configing /etc/glusterfs/glusterd.vol with "option transport.socket.bind-address 192.168.121.45' to listen on 192.168.121.45.
And I config /etc/glusterfs/glusterd.vol with "option transport.socket.bind-address 192.168.121.45" and I stop and start vol.
I find brick start with '--xlator-option transport.socket.bind-address=192.168.121.45'， but brick listens on 0.0.0.0 instead of 192.168.121.45.

cat /etc/glusterfs/glusterd.vol
volume management
type mgmt/glusterd
option transport.socket.read-fail-log off
option transport.socket.keepalive-interval 2
option working-directory /var/lib/glusterd
option strict-auth-accept on
option transport.socket.listen-port 24007
option transport.socket.keepalive-time 10
option event-threads 1
option transport-type socket
option max-port 60999
option ping-timeout 0
#option transport.address-family inet6
# option lock-timer 180
# option base-port 49152
option transport.socket.bind-address 192.168.121.45
end-volume

ps aux |grep glusterfsd
root 5063 0.4 0.0 752948 13608 ? Ssl 19:15 0:00 /usr/sbin/glusterfsd -s 192.168.121.45 --volfile-id test.192.168.121.45.mnt-test -p /var/run/gluster/vols/test/192.168.121.45-mnt-test.pid -S /var/run/gluster/e0446444a49588df.socket --brick-name /mnt/test -l /var/log/glusterfs/bricks/mnt-test.log --xlator-option *-posix.glusterd-uuid=a79ebee4-fb76-4029-bc7c-db411d2bbadb --process-name brick --brick-port 49152 --xlator-option test-server.listen-port=49152 --xlator-option transport.socket.bind-address=192.168.121.45

netstat -apn |grep 5063
tcp 0 0 0.0.0.0:49152 0.0.0.0:* LISTEN 5063/glusterfsd

The exact command to reproduce the issue:

The full output of the command that failed:

Expected results:

Mandatory info:
- The output of the gluster volume info command:

- The output of the gluster volume status command:

- The output of the gluster volume heal command:

**- Provide logs present on following locations of client and server nodes -
/var/log/glusterfs/

**- Is there any crash ? Provide the backtrace and coredump

Additional info:

- The operating system / glusterfs version:

Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration

[zhangxyue]

maybe we need use transport.socket.bind-address like listen-port in glusterd_volume_start_glusterfs.