Unable to associate brick gluster1.mydomain.com:/bricks/brick1/data with a peer in the cluster

[ach-nke]

I'm getting error when trying to run gstatus on nodes[2:3] of the cluster. It only works on node1.

[root@gluster2 ~]# gstatus -a -o json
Unable to associate brick gluster1.mydomain.com:/bricks/brick1/data with a peer in the cluster, possibly due
to name lookup failures. If the nodes are not registered (fwd & rev)
to dns, add local entries for your cluster nodes in the the /etc/hosts file

Here is my peer status:

[root@gluster2 ~]# gluster peer status
Number of Peers: 2

Hostname: 10.10.10.5
Uuid: bbb19d4b-c9fc-4f14-8a9c-9cedf1fac367
State: Peer in Cluster (Connected)
Other names:
gluster1.mydomain.com

Hostname: gluster3.mydomain.com
Uuid: da74fc61-eb2a-4f0d-906b-9fc2c287908f
State: Peer in Cluster (Connected)

As you may notice my node1 hostname is IP address. According to documentation:

Note: When using hostnames, the first server needs to be probed from one other server to set its hostname.

I did that, and the hostname appeared in Other names

And here is my gluster volume config:

[root@gluster2 ~]# gluster volume info
Volume Name: data
Type: Replicate
Volume ID: 8f8285bc-c8b2-4112-b88e-49df45bf7e87
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: gluster1.mydomain.com:/bricks/brick1/data
Brick2: gluster2.mydomain.com:/bricks/brick1/data
Brick3: gluster3.mydomain.com:/bricks/brick1/data
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off

[ach-nke]

I figured out how to fix peer naming:

1. create cluster
2. remove node1
3. re-add node1 from another node