[Bugs] [Bug 1208255] New: 'volume heal $volname info' shows FQDNs instead of provided hostnames for nodes

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1208255

            Bug ID: 1208255
           Summary: 'volume heal $volname info' shows FQDNs instead of
                    provided hostnames for nodes
           Product: GlusterFS
           Version: 3.5.3
         Component: BDB
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: jheese at inetu.net
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
The 'gluster volume $volname info' command shows the FQDN hostnames of the
nodes instead of the hostnames provided to Gluster  during volume creation
(when they differ).

Version-Release number of selected component (if applicable):
[root at duke ~]# gluster --version
glusterfs 3.5.3 built on Nov 13 2014 11:06:07
(Also saw the same behavior on 3.6.2-1 from RPMs at
http://download.gluster.org/pub/gluster/glusterfs/LATEST/CentOS/epel-6.6/x86_64/)

How reproducible:
100%

Steps to Reproduce:
1. Create glusterfs volume on two Gluster nodes using hostname aliases (eg.
configured in /etc/hosts) different from system-configured fully-qualified
hostname:

# gluster volume create gluster_vol replica 2 node1-ib:/bricks/brick1
node2-ib:/bricks/brick1

2. Start glusterfs volume:

# gluster volume start gluster_vol

3. Show gluster heal info:

# gluster volume heal gluster_vol info

Actual results:
Brick node1.localdomain.net:/bricks/brick1/
Number of entries: 0

Brick node2.localdomain.net:/bricks/brick1/
Number of entries: 0

Expected results:
Brick node1-ib:/bricks/brick1/
Number of entries: 0

Brick node2-ib:/bricks/brick1/
Number of entries: 0

Additional info:
This appears to be a 'display-only' kind of bug -- the Gluster replication
traffic appears to be using the proper hostnames/IPs -- it just doesn't render
the "heal info" output properly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.