+++ This bug was initially created as a clone of Bug #1101691 +++ Description of problem: ------------------------ Spelling correction in glusterd logs wrt log message describing enabling/disabling barrier Version-Release number of selected component (if applicable): ------------------------------------------------------------- mainline How reproducible: ------------------ Not Applicable Steps to Reproduce: -------------------- 1. Enable/ disable barrier 2. Notice the glusterd logs Actual results: --------------- "Received" was misspelt as "Recieved" Expected results: ----------------- Spelling mistake should be corrected Additional info: ----------------- <snip> [2014-05-27 23:34:45.404075] I [glusterd-handler.c:3998:__glusterd_handle_barrier] 0-management: Recieved barrier volume request for volume drvol [2014-05-27 23:35:34.730015] I [glusterd-handler.c:3998:__glusterd_handle_barrier] 0-management: Recieved barrier volume request for volume drvol </snip>
Since this has not made into downstream, marking the status back to assigned.
removing FailedQA tag from this bug, as its not actually a failure
The fix is already into upstream with http://review.gluster.org/7902 BZ should be moved to 'Modified' the moment branching takes place.
Verified with glusterfs-3.7.0-2.el6rhs <snip_from_glusterd_logs> [2015-05-28 07:20:45.465698] I [glusterd-handler.c:4288:__glusterd_handle_barrier] 0-management: Received barrier volume request for volume rvol </snip_from_glusterd_logs> marking this bug as VERIFIED
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. https://rhn.redhat.com/errata/RHSA-2015-1495.html