Description of problem: ======================= Peer status showing identical hostname and other names in the peer status. Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.7.5-19 How reproducible: ================= Always Steps to Reproduce: =================== 1. Have three nodes (n1, n2 and n3) with glusterfs-3.7.5-19 build 2. Probe node n2 from node n1 3. Again probe node n3 from node n2 4. Check peer status in all the nodes // In n1 node, you will see issue specified above Actual results: =============== Host name and other names are identical in peer status Expected results: ================== hostname and other names should be different in peer status Additional info:
This happens *only* when the IP address is used in peer probe. Although it seems like a bug but considering there is no functionality impact and our recommendation is to use fqdn instead of IP lowering down the priority and severity.
Observed same result even if i used the host name (AWS public DNS name)
Issue is not getting after multiple trials with latest code base, hence closing the issue.
Issue is not getting reproduced after multiple trials with latest code base, hence closing the bug