Bug 1199033

Summary:	[epoll] Typo in the gluster volume set help message for server.event-threads and client.event-threads
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Anil Shah <ashah>
Component:	glusterfs	Assignee:	Satish Mohan <smohan>
Status:	CLOSED ERRATA	QA Contact:	Anil Shah <ashah>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.0	CC:	bsrirama, byarlaga, nbalacha, nlevinki, sankarshan, sasundar, smohan, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.5-0.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1199382 (view as bug list)		Environment:
Last Closed:	2016-03-01 05:23:13 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:
Bug Blocks:	1260783

Description Anil Shah 2015-03-05 11:05:19 UTC

Description of problem:

Typo in gluster volume set help message for server.event-threads and client.event-threads

Description: Specifies the number of event threads to execute inin parallel. Larger values would help process responses faster, depending on available processing power. Range 1-32 threads.

Typo is inin word is repeated twice.

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

glusterfs 3.6.0.47

How reproducible:

100%

Steps to Reproduce:
1. gluster v set help 
2. search client.event-threads and client.event-threads




Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 3 Anand Nekkunti 2015-10-19 10:12:27 UTC

Upstream patch : http://review.gluster.org/#/c/9816/

Due to rebase with 3.7.5 branch, patch is pulled to downstream 3.1.2 branch.
So moving on_qa

Comment 4 Byreddy 2015-10-19 12:13:57 UTC

Verified this bug  with version - glusterfs-3.7.5-0.3.

Both Client and Server Description verified and the message is proper.

Moving to verified state.

Comment 8 errata-xmlrpc 2016-03-01 05:23:13 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/RHBA-2016-0193.html