Bug 1674598

Summary:	Remove the validation on acceptable latency during gluster deployment
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhhiv-1.6	CC:	pasik, rhs-bugs, sabose
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHHI-V 1.6.z Async Update
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1674600 (view as bug list)		Environment:
Last Closed:	2019-10-03 12:23:57 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:	1674600
Bug Blocks:

Description Gobinda Das 2019-02-11 16:34:10 UTC

Description of problem:
 Now we don't have validation for Storage disks are writable or not and acceptable latency during gluster deployment

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 SATHEESARAN 2019-02-20 10:42:51 UTC

There is no clear requirement on the value of storage latency and deferring this bug for RHHI-V 1.7

Comment 3 SATHEESARAN 2019-03-28 08:21:21 UTC

There has been a clarity now on the dependent bug

Comment from Sahina:
     Latency requirement for sanlock = write 1MB with bs=512 odirect=yes within 10s

Comment 6 Yaniv Kaul 2019-07-22 08:30:01 UTC

Status?

Comment 7 Sahina Bose 2019-07-22 10:05:05 UTC

This is a tracker bz - the dependent bz is verified. updating the status of this

Comment 8 SATHEESARAN 2019-08-12 07:38:47 UTC

Verified with  latest gluster-ansible-features-1.0.4-5 with RHGS 3.4.4

Latency check was now removed.

Comment 10 errata-xmlrpc 2019-10-03 12:23:57 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:2963