+++ This bug was initially created as a clone of Bug #963534 +++ Description of problem: glusterd logs (wrongly) indicate that a node responded to itself, although it actually responded to one of its peers, in the function glusterd_xfer_friend_add_resp(). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Have a cluster of two nodes N1 and N2, 2. Restart glusterd on both of them after ensuring they are both connected to each other. 3. Check the glusterd logs. Actual results: N1's glusterd logs say "Responded to N1" when it responded to N2, and vice versa, thereby rendering the logs extremely misleading while debugging issues of the kind https://bugzilla.redhat.com/show_bug.cgi?id=962266 and https://bugzilla.redhat.com/show_bug.cgi?id=961703. Expected results: In step 3, N1's glusterd logs must say "Responded to N2" when it responds to N2 and vice versa. Additional info:
REVIEW: http://review.gluster.org/5017 (glusterd: Fix misleading log messages of the kind "Node <n> responded to <n>") posted (#1) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/5017 committed in master by Vijay Bellur (vbellur) ------ commit db18b17c88c1976f9e523c4c6712c7e444927cc4 Author: Krutika Dhananjay <kdhananj> Date: Thu May 16 10:43:54 2013 +0530 glusterd: Fix misleading log messages of the kind "Node <n> responded to <n>" PROBLEM: glusterd logs coming from glusterd_xfer_friend_add_resp() (wrongly) indicate that a node responded to itself, although it actually responded to one of its peers. FIX: Make glusterd_xfer_friend_add_resp() distinguish between remote host and self and print the appropriate hostname. Change-Id: I2a504eeb058c08a0d378443888eb6f1dc7edc76f BUG: 963537 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/5017 Reviewed-by: Amar Tumballi <amarts> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Gluster Build System <jenkins.com>