Bug 1440638

Summary: [RFE]: Testing effort tracker for new EC variants 8+2 and 16+4
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rahul Hinduja <rhinduja>
Component: disperseAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED ERRATA QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: amukherj, asrivast, rhs-bugs, storage-qa-internal
Target Milestone: ---Keywords: FutureFeature
Target Release: RHGS 3.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-21 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-21 04:37:54 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: 1417138    

Description Rahul Hinduja 2017-04-10 07:33:54 UTC 
Description of problem:
=======================

One of the 3.3.0 requirement is to test the new variants of EC (8+2 and 16+4). In total following to be tested:

Enhance supported configurations for EC (4+2, 8+2, 16+4, 8+4)

Raising this bug to track the testing effort for 3.3.0. Also to have a doc bug corresponding to this engineering bug.
Comment 4 Nag Pavan Chilakam 2017-04-25 12:00:36 UTC 
QA_validation:
Able to create a 8+2 and 16+4 volume successfully and ec properties propograte well with issues. File distribution also works well.
As sanity is working well ,hence moving to verified
Note:that further testing will be still carried forward and will raise any bugs seperately

test version:3.8.4-23
Comment 5 Nag Pavan Chilakam 2017-04-25 12:08:50 UTC 
Further Testing activites:
1) we will run basic ec validation including heals on the 2 new varients
2) the majority of testing will still be carried on 4+2 due to limited resources
Comment 7 errata-xmlrpc 2017-09-21 04:37:54 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-2017:2774