Bug 1312727 - Identical host name and other names in peer status
Identical host name and other names in peer status
Status: CLOSED WORKSFORME
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.1
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Gaurav Yadav
storage-qa-internal@redhat.com
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-29 00:27 EST by Byreddy
Modified: 2017-08-17 10:33 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-17 09:59:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Byreddy 2016-02-29 00:27:34 EST
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:
Comment 3 Atin Mukherjee 2016-02-29 00:45:21 EST
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.
Comment 4 RajeshReddy 2016-02-29 02:02:28 EST
Observed same result even if i used the host name (AWS public DNS name)
Comment 7 Gaurav Yadav 2017-08-17 09:59:45 EDT
Issue is not getting after multiple trials with latest code base, hence closing the issue.
Comment 8 Gaurav Yadav 2017-08-17 10:33:26 EDT
Issue is not getting reproduced after multiple trials with latest code base, hence closing the bug

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