Bug 1638625 - [gluster-ansible] Revert XFS related changes from gluster-ansible role
Summary: [gluster-ansible] Revert XFS related changes from gluster-ansible role
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHHI-V 1.5
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1638626
Blocks: 1520836
TreeView+ depends on / blocked
 
Reported: 2018-10-12 06:10 UTC by SATHEESARAN
Modified: 2019-05-20 04:55 UTC (History)
3 users (show)

Fixed In Version: gluster-ansible-roles-1.0.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1638626 (view as bug list)
Environment:
Last Closed: 2019-05-20 04:55:46 UTC
Embargoed:

Attachments (Terms of Use)

Description SATHEESARAN 2018-10-12 06:10:35 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 4 SATHEESARAN 2018-10-12 08:43:08 UTC 
Raised blocker flag as this bug involves changing XFS max_retries params which is not required for RHEL 7.6
Comment 5 SATHEESARAN 2018-10-17 01:45:16 UTC 
The fixes for this bug is already available. Moving this bug to MODIFIED state
Comment 6 SATHEESARAN 2018-10-17 01:46:13 UTC 
The dependent gluster-ansible bug is already ON_QA
Comment 7 SATHEESARAN 2018-10-17 05:21:58 UTC 
Tested with gluster-ansible-roles-1.0.3

XFS max_retries related changes are not done now.
Note You need to log in before you can comment on or make changes to this bug.