Bug 1638626

Summary:	[gluster-ansible] Revert XFS related changes from gluster-ansible role
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gluster-ansible	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.4	CC:	rcyriac, rhs-bugs, sabose, sankarshan, sasundar
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.z Batch Update 1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-roles-1.0.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1638625	Environment:
Last Closed:	2018-10-31 08:42:30 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:	1638625

Description SATHEESARAN 2018-10-12 06:13:22 UTC

Description of problem:
-----------------------
Bug 1523562 was fixed to include XFS max_retries for the case of XFS on VDO volumes. With the information from Bryan Gurney on the bug 1578353, this change is no longer required.

This bug is filed to have that earlier XFS max_retries change to be removed from gluster-ansible-roles

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
gluster-ansible-roles-1.0.2-2

How reproducible:
-----------------
Always

Expected results:
------------------
Remove the change that came in with effect of BZ 1523562

Comment 2 SATHEESARAN 2018-10-17 05:21:43 UTC

Tested with gluster-ansible-roles-1.0.3

XFS max_retries related changes are not done now.

Comment 4 errata-xmlrpc 2018-10-31 08:42:30 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-2018:3428