Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1456580

Summary: [Doc] Example in Erasure Code Profiles report unsupported configuration
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Andrea Perotti <aperotti>
Component: DocumentationAssignee: Aron Gunn <agunn>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: low Docs Contact:
Priority: unspecified    
Version: 2.3CC: agunn, asriram, hgurav, kdreyer, tcole, vumrao
Target Milestone: rc   
Target Release: 2.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-23 09:53:36 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: 1465789    

Description Andrea Perotti 2017-05-29 16:36:16 UTC 
Description of problem:

In chapter "5.2. Erasure Code Profiles" of Red Hat Ceph Storage Guide

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html-single/storage_strategies_guide/#erasure_code_profiles

is reported an example for the creation of an erasure code profile of 3+2, but at the time of writing the closest config supported is 4+2 (ref: 
* https://access.redhat.com/articles/1548993
* https://access.redhat.com/solutions/2094441 )

Is expected that documentation do not offer examples of unsupported configuration, and even if the future will expand the supported configuration, would be better to show safest examples from a supportability PoV.
Comment 3 Tupper Cole 2017-11-08 21:51:36 UTC 
By the same token- should the default EC profile be a supported profile rather than k=2 m=1?
Comment 4 Giridhar Ramaraju 2019-08-05 13:10:21 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 5 Giridhar Ramaraju 2019-08-05 13:11:25 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 6 Giridhar Ramaraju 2019-08-20 07:19:46 UTC 
Level setting the severity of this defect to "Low" with a bulk update. Pls
refine it to a more closure value, as defined by the severity definition in
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity