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.
By the same token- should the default EC profile be a supported profile rather than k=2 m=1?
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
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