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:
Since wrong messages in logs can lead to delay in debugging any customer issues, I am marking this a high priority.
Tested with glusterfs-3.4.0.11rhs-1.
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