Description of problem: --------------------------------------- After performing peer probe from a machine with an operating-version of 1, to a machine of operating-version 2, the following is seen on running 'gluster peer status' - Number of Peers: 1 Hostname: 10.70.35.13 Port: 24007 Uuid: 00000000-0000-0000-0000-000000000000 State: Establishing Connection (Disconnected) The following is seen in the logs - --------------------------------------- [2012-12-10 00:20:00.588664] W [socket.c:400:__socket_rwv] 0-management: readv failed (No data available) [2012-12-10 00:20:03.592665] E [glusterd-handshake.c:755:glusterd_mgmt_hndsk_version_cbk] 0-management: failed to validate the operating version of peer (10.70.35.13) Version-Release number of selected component (if applicable): glusterfs 3.4.0qa4 How reproducible: Always Steps to Reproduce: 1.Peer probe from a machine of operating version 1 to a machine of operating version 2. Actual results: Peer probe is not successful. Expected results: Peer probe should succeed. Additional info:
(In reply to comment #0) > Expected results: > Peer probe should succeed. The expected result is that probe should throw the right error message. Probe shouldn't succeed in this case.
CHANGE: http://review.gluster.org/4293 (glusterd: fix peer probe cli response on error) merged in master by Anand Avati (avati)
The issue is still seen in glusterfs 3.4.0qa5. Moving the bug to MODIFIED state.
Verified in glusterfs 3.4.0qa8. Peer probe from a node which is at a lower op-version to a node which is at a higher op-version now fails with an error message - "peer probe: failed: Peer <IP> is already at a higher op-version"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html