To recreate the problem, In peer1: Perform the following: gluster volume create <volname> <brick1> gluster volume add <volname> <brick2> gluster peer probe peer2 gluster peer status The peer list has peer2 in connected (rejected) state. This makes it impossible for using peer2 in any volume operation.
CHANGE: http://review.gluster.com/264 (Change-Id: Ia2d89fd919b077232a37debc2aebe1bc72150856) merged in release-3.2 by Vijay Bellur (vijay)
CHANGE: http://review.gluster.com/285 (Change-Id: Ia2d89fd919b077232a37debc2aebe1bc72150856) merged in master by Vijay Bellur (vijay)
CHANGE: http://review.gluster.com/258 (Change-Id: Iec33deaff338a6b48e5015785711de3c8bc9fb2e) merged in release-3.1 by Vijay Bellur (vijay)
Works fine on 3.2.3. On 3.1.7 verification pending on lakshmipathi for a patch for glusterfs.spec file for rpm creation
*** Bug 3425 has been marked as a duplicate of this bug. ***
CHANGE: http://review.gluster.com/351 (Change-Id: Ib0045149fcdfcfb801b2f1f0a10417b04e294fef) merged in release-3.1 by Vijay Bellur (vijay)
CHANGE: http://review.gluster.com/365 (Change-Id: I3e71461c5a8c5b0d24006f24ad762bb4689ac341) merged in release-3.1 by Vijay Bellur (vijay)