Bug 1700814

Summary:	Add GB_CLI_TIMEOUT env configuration in rhgs-server-container template/container scripts.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Humble Chirammal <hchiramm>
Component:	rhgs-server-container	Assignee:	Saravanakumar <sarumuga>
Status:	CLOSED ERRATA	QA Contact:	Nitin Goyal <nigoyal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	akrishna, knarra, kramdoss, madam, nigoyal, pasik, rcyriac, rhs-bugs, sankarshan, sarumuga, suprasad
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, gluster block volume creation failed as the time out value was inadequate for large volumes. As a fix, users can increase the timeout value to 15 minutes (900 seconds) so that gluster block volume creation is successful even for a large volume size of 2 TB.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-13 19:18:59 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:	1665543

Description Humble Chirammal 2019-04-17 12:13:33 UTC

Description of problem:

As part of fixing https://bugzilla.redhat.com/show_bug.cgi?id=1665543 , gluster block has introduced a new env variable called "GB_CLI_TIMEOUT" in gluster block configuration file.

$ cat /etc/sysconfig/gluster-blockd
GB_CLI_TIMEOUT=900

We have to provide an option in our rhgs-server-container template/startup script to configure this environment variable. This bugzilla track the same.

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

OCS 3.11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 Anjana KD 2019-06-03 12:54:16 UTC

Have updated the doc text. Kindly review it for technical accuracy.

Comment 9 Anjana KD 2019-06-04 10:49:17 UTC

Have updated the changes. Thankyou.

Comment 11 errata-xmlrpc 2019-06-13 19:18:59 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://access.redhat.com/errata/RHBA-2019:1406