Bug 1187187 - Gluster peer probe status shows IP address from the replica pair instead hostname.
Summary: Gluster peer probe status shows IP address from the replica pair instead host...
Keywords:
Status: CLOSED DUPLICATE of bug 1120437
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-29 13:55 UTC by Triveni Rao
Modified: 2016-05-16 04:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-29 17:47:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Triveni Rao 2015-01-29 13:55:20 UTC
Description of problem:
Gluster peer probe status shows IP address from the replica pair instead hostname.

when gluster nodes are porbed from a serverA then peer status from the server shows proper name of the replica serverB but when the gluster peer status is executed on the replica serverB then it shows IP address of the serverA instead hostname.


Version-Release number of selected component (if applicable):

[root@rhsauto032 vol5]# rpm -qa | grep gluster
gluster-nagios-common-0.1.4-1.el6rhs.noarch
glusterfs-libs-3.6.0.42-1.el6rhs.x86_64
gluster-nagios-addons-0.1.14-1.el6rhs.x86_64
samba-glusterfs-3.6.509-169.4.el6rhs.x86_64
glusterfs-api-3.6.0.42-1.el6rhs.x86_64
glusterfs-fuse-3.6.0.42-1.el6rhs.x86_64
glusterfs-server-3.6.0.42-1.el6rhs.x86_64
glusterfs-geo-replication-3.6.0.42-1.el6rhs.x86_64
glusterfs-rdma-3.6.0.42-1.el6rhs.x86_64
vdsm-gluster-4.14.7.3-1.el6rhs.noarch
glusterfs-3.6.0.42-1.el6rhs.x86_64
glusterfs-cli-3.6.0.42-1.el6rhs.x86_64
[root@rhsauto032 vol5]#


[root@rhsauto032 vol5]# glusterfsd --version
glusterfs 3.6.0.42 built on Jan  8 2015 13:04:55
Repository revision: git://git.gluster.com/glusterfs.git

How reproducible:

Frequently reproducible.

Steps to Reproduce:
1.Gluster peer status from serverA
2.its hows replica server's hostname properly.
3.Gluster peer status executed from serverB then it shows IP of ServerA instead the hostname.

Actual results:


[root@rhsauto032 bricks]# gluster peer status
Number of Peers: 1

Hostname: rhsauto034.lab.eng.blr.redhat.com
Uuid: 68771e4c-8a0c-46ab-b2bd-2842b1dff0d2
State: Peer in Cluster (Connected)
[root@rhsauto032 bricks]# 


root@rhsauto034 ~]# gluster peer status
Number of Peers: 1

Hostname: 10.70.37.7
Uuid: 87064cb7-13aa-4a43-94cb-bd1da392bb94
State: Peer in Cluster (Connected)
[root@rhsauto034 ~]# 

Expected results:

Expected hostname instead of IP address in the output.

Additional info:

Comment 2 SATHEESARAN 2015-01-29 17:47:54 UTC
Hi Triveni,

This is a KNOWN_ISSUE.
This is because, glusterd doesn't perform a reverse lookup once it receives the peer probe request from a node.

This issue is tracked with the bug - 1120437
Closing this bug as DUPLICATE of above mentioned bug.

Feel free re-open this bug, if you feel otherwise.

*** This bug has been marked as a duplicate of bug 1120437 ***


Note You need to log in before you can comment on or make changes to this bug.