Bug 844279 - Inconsistent output of "gluster peer status". Some nodes show up with hostname, others with IP
Summary: Inconsistent output of "gluster peer status". Some nodes show up with hostnam...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Kaushal
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 07:57 UTC by Patric Uebele
Modified: 2013-09-15 23:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-04 08:14:30 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 201933 0 None None None 2012-09-04 10:15:15 UTC

Description Patric Uebele 2012-07-30 07:57:55 UTC
Description of problem:
When running "gluster peer status" on several storage nodes of the same trusted storage pool, some nodes show up with their hostnames, some with their IP, despite having the same network settings (hosts, resolv.conf, nsswitch,conf).

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


How reproducible:
reproducible

Steps to Reproduce:
1.run gluster peer status on multipe storage servers of the pool
2.
3.
  
Actual results:
[root@rhs1-1 ~]# gluster peer status
Number of Peers: 2

Hostname: 192.168.122.12
Uuid: a4e7a8c4-0985-4f11-ad1f-ee730bcd7320
State: Peer in Cluster (Connected)

Hostname: rhs1-3
Uuid: bc3609b3-f30e-4231-9b5f-9af878c5ca84
State: Peer in Cluster (Connected)

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

Hostname: 192.168.122.11
Uuid: 8499bba0-f1f0-47c4-ab0e-6236156105b8
State: Peer in Cluster (Connected)

Hostname: rhs1-3
Uuid: bc3609b3-f30e-4231-9b5f-9af878c5ca84
State: Peer in Cluster (Connected)

[root@rhs1-3 ~]# gluster peer status
Number of Peers: 2

Hostname: 192.168.122.11
Uuid: 8499bba0-f1f0-47c4-ab0e-6236156105b8
State: Peer in Cluster (Connected)

Hostname: 192.168.122.12
Uuid: a4e7a8c4-0985-4f11-ad1f-ee730bcd7320
State: Peer in Cluster (Connected)


Expected results:
Hostname row should show hostname in every case.


Additional info:

Comment 2 Niels de Vos 2012-07-30 09:53:21 UTC
How did you 'gluster peer probe' the storage servers? Was it by IP or by hostname?

You can have the hostname updated if you peer-probe the storage server again by hostname. Sometimes it is needed to do the peer-probe from both storage servers:

(rhss01) # gluster peer probe server rhss02.example.com
(rhss02) # gluster peer probe server rhss01.example.com

Does this help?

Comment 3 Niels de Vos 2012-07-30 09:56:39 UTC
hmm, of course there is a 'server' too much in the 'gluster peer probe' commands :-/

Comment 4 Patric Uebele 2012-07-31 09:17:31 UTC
(In reply to comment #2)
> How did you 'gluster peer probe' the storage servers? Was it by IP or by
> hostname?
> 
I did add them by hostname:
# gluster peer probe rhs1-2


> You can have the hostname updated if you peer-probe the storage server again
> by hostname. Sometimes it is needed to do the peer-probe from both storage
> servers:
> 
> (rhss01) # gluster peer probe server rhss02.example.com
> (rhss02) # gluster peer probe server rhss01.example.com
> 
> Does this help?

Yes, this does fix it.

Comment 5 Amar Tumballi 2012-09-04 08:14:30 UTC
Thanks for confirming. This involves lot of changes internally to make it work consistently. Hence, for now, lets handle this issue using the work around suggested by ndevos.

Comment 6 Patric Uebele 2012-09-04 09:27:43 UTC
Could you make sure that the workaround is mentioned in the release notes?

Thanks,

Patric

Comment 7 Niels de Vos 2012-09-04 10:15:15 UTC
I'll write this up for the Red Hat Customer Portal at https://access.redhat.com/knowledge/solutions/201933


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