[Bugs] [Bug 1314366] New: Peer information is not propagated to all the nodes in the cluster, when the peer is probed with its second interface FQDN/IP

[bugzilla at redhat.com]

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

            Bug ID: 1314366
           Summary: Peer information is not propagated to all the nodes in
                    the cluster, when the peer is probed with its second
                    interface FQDN/IP
           Product: GlusterFS
           Version: 3.7.8
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: sasundar at redhat.com
                CC: bugs at gluster.org



Description of problem:
-----------------------
When there are multiple interfaces available in the gluster node and to make
use both the interfaces for gluster traffic, the peer probe should be done with
all the network identifiers (i.e) IP or FQDN

While doing so, the other names for the particular peer is updated.
The problem here is that the other name of the particular host is not
propogated to all the nodes in the cluster, leading to error - "staging failed
on the host" - on the other hosts, for any volume related operation, as that
node is unaware of the new hostname or IP

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

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Create 3 gluster nodes with 2 network interfaces and each of them connected
to different (isolated) network
2. Form a gluster cluster with 2 gluster nodes by peer probing with one set of
IP ( from network1 )
3. Probe the node2 ( from node1 ) with IP ( from network2 )
4. Check peer status on both the nodes
5. From node1, peer probe node3 with IP from network1
6. From node1, peer probe node3 with IP from network2

Actual results:
---------------
Peer status on node2 doesn't get updated with other name of node3

Expected results:
-----------------
Peer information should be consistent/updated across all the nodes in the
cluster

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