Bug 860543

Summary:	Typo with common errors (like received instead of recieved).
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	vpshastry <vshastry>
Component:	glusterfs	Assignee:	vpshastry <vshastry>
Status:	CLOSED ERRATA	QA Contact:	senaik
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	nsathyan, rhs-bugs, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0qa5-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 22:33:25 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:

Description vpshastry 2012-09-26 06:10:28 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
availble
Recieved
recieved
Unkown

Expected results:
available
Received
received
Unknown


Additional info:

Comment 2 senaik 2013-01-03 11:57:42 UTC

Verified in glusterfs 3.4.0qa5 

'Received' and 'received' were verified in rebalance logs . 

Verification Steps : 

On a distributed volume , added a new brick and stopped a running rebalance process :
gluster v rebalance dist start ; gluster v rebalance dist status; gluster v rebalance dist stop 

------Part of rebalance log--------------

[2013-01-02 10:02:53.425192] I [dht-rebalance.c:1686:gf_defrag_stop] 0-: Received stop command on rebalance
[2013-01-02 10:02:53.433171] W [glusterfsd.c:969:cleanup_and_exit] (-->/lib64/libc.so.6(clone+0x6d) [0x3ca1ee5ccd] (-->/lib64/libpthread.so.0() [0x3ca
26077f1] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xcd) [0x40523d]))) 0-: received signum (15), shutting down

--------------------------------------------- 
Could not find scenario to check 'Available' and 'Unknown' . 
Checked in Source Code and the typos are fixed . Hence marking it as verified .

Comment 3 Scott Haines 2013-09-23 22:33:25 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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html