Bug 1101697

Summary: [barrier] Spelling correction in glusterd log message while enabling/disabling barrier
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: glusterdAssignee: Gaurav Kumar Garg <ggarg>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: low Docs Contact:
Priority: high    
Version: rhgs-3.0CC: amukherj, ggarg, gluster-bugs, kparthas, nlevinki, smohan, vagarwal, vbellur
Target Milestone: ---   
Target Release: RHGS 3.1.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.7.0-2.el6rhs Doc Type: Bug Fix
Doc Text:
There was some typo spelling correction issue in barrier log messages. with this fix it will show correct barrier log message.
Story Points: ---
Clone Of: 1101691 Environment:
Last Closed: 2015-07-29 04:32:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1101691    
Bug Blocks: 1202842    

Description SATHEESARAN 2014-05-27 18:17:34 UTC
+++ 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>

Comment 1 Atin Mukherjee 2014-07-14 06:08:02 UTC
Since this has not made into downstream, marking the status back to assigned.

Comment 2 SATHEESARAN 2014-07-16 17:45:56 UTC
removing FailedQA tag from this bug, as its not actually a failure

Comment 3 Atin Mukherjee 2015-04-02 04:12:06 UTC
The fix is already into upstream with http://review.gluster.org/7902
BZ should be moved to 'Modified' the moment branching takes place.

Comment 6 SATHEESARAN 2015-05-28 02:00:01 UTC
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

Comment 8 errata-xmlrpc 2015-07-29 04:32:07 UTC
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