Description of problem: Execution of 'gluster peer probe <ip_address>' is not successful. Glusterd Log: ------------- [2012-02-24 20:15:33.345982] E [glusterd-utils.c:2209:glusterd_import_volinfo] 0-glusterd: volume1.rebalance missing in payload for dist [2012-02-24 20:15:33.346084] E [glusterd-sm.c:1002:glusterd_friend_sm] 0-glusterd: handler returned: -2 Actual Results:- ------------------ [root@APP-SERVER1 ~]# gluster volume replace-brick dist 192.168.2.35:/export1 192.168.2.36:/export1 start 192.168.2.36, is not a friend [root@APP-SERVER1 ~]# gluster peer probe 192.168.2.36 [root@APP-SERVER1 ~]# echo $? 110 [root@APP-SERVER1 ~]# gluster peer probe 192.168.2.36 Probe on host 192.168.2.36 port 24007 already in peer list [root@APP-SERVER1 ~]# gluster peer detach 192.168.2.36 [root@APP-SERVER1 ~]# echo $? 110 [root@APP-SERVER1 ~]# gluster peer status Number of Peers: 1 Hostname: 192.168.2.36 Uuid: 5d16bbd9-065d-486d-9f3b-51d888a73fee State: Probe Sent to Peer (Connected) [root@APP-SERVER1 ~]# gluster peer detach 192.168.2.36 [root@APP-SERVER1 ~]# echo $? 110 [root@APP-SERVER1 ~]# gluster volume replace-brick dist 192.168.2.35:/export1 192.168.2.36:/export1 start 192.168.2.36, is not befriended at the moment [root@APP-SERVER1 ~]# gluster peer probe 192.168.2.35 Probe on localhost not needed [root@APP-SERVER1 ~]# gluster peer probe 192.168.2.36 Probe on host 192.168.2.36 port 24007 already in peer list [root@APP-SERVER1 ~]# [root@APP-SERVER1 ~]# gluster volume replace-brick dist 192.168.2.35:/export1 192.168.2.36:/export1 start 192.168.2.36, is not befriended at the moment Version-Release number of selected component (if applicable): mainline
CHANGE: http://review.gluster.com/2814 (mgmt/glusterd: pass defrag_cmd in rsp dict for volume info) merged in master by Vijay Bellur (vijay)
Bug is fixed . verified on 3.3.0qa39