Fixing issue with multiple interface used in brick creation and gluster peer probe

[GowthamShanmugam]

gluster won't allow creating gluster peer probe with one ip and brick creation using another ip.

storage node1:
eth0: 10.70.43.186
eth1: 10.70.42.230

storage node2:
eth0: 10.70.43.151
eth1: 10.70.42.231

storage node3:
eth0: 10.70.43.153
eth1: 10.70.43.14

from 10.70.43.186 (all eth0)
gluster peer probe 10.70.43.151
gluster peer probe 10.70.43.153

gluster peer status:

Number of Peers: 2

Hostname: 10.70.43.151
Uuid: 3f088d2b-105a-4a3d-817f-88cc2ce9cc10
State: Peer in Cluster (Connected)

Hostname: 10.70.43.153
Uuid: 7e81cdd5-5dad-458c-9bdc-db8abe574e7e
State: Peer in Cluster (Connected)

gluster volume create V1 10.70.42.230:/root/glusters/b1 10.70.42.231:/root/glusters/b1 10.70.43.14:/root/glusters/b1 force (all eth1)
volume create: V1: failed: Host 10.70.42.231 is not in 'Peer in Cluster' state

But if we do peer probe using the following step then multiple interfaces is possible:

1. peer probe node B using eth1 from node A
2. now do peer probe for node c from node B

if you see peer probe status hostname of node B is in the other name :

Hostname: 10.70.42.231
Uuid: 42422510-bb1c-42f8-b324-00658e2371ca
State: Peer in Cluster (Connected)
Other names:
dhcp43-151.lab.eng.blr.redhat.com

Hostname: 10.70.43.186
Uuid: 568a2fbe-7f8c-4d38-a01c-b1cca1879d36
State: Peer in Cluster (Connected)

so now we can create brick using eth1 event peer probe is done by eth0

so if we use socket.getbyhostname("10.70.42.231"), it always gives ip of 10.70.43.151.

So peer probe hostname won't match with brick hostname again. So no brick for that node is displayed.

Here the problem is an other_name field.

[GowthamShanmugam]

This issue is fixed