Description of problem (please be detailed as possible and provide log snippests): With multi SC feature introduced, creating a new storage class the failure domain is missing. Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install ocp4.6 and ocs4.5 2. Create new storage class from UI with new pool Actual results: The storage class is lucking failure domain Expected results: Should be failure domain (default one is rack) Additional info:
The UI is creating the pool CR, isn't one of the inputs from the UI the desired failure domain? If a failure domain is not specified, "host" will be the default for the pool. We should default to the same value that the OCS operator is using. If there are at least three zones, "zone" should be the failure domain. If +1 scaling, "host" should be the default. Otherwise, "rack".
There is no way to input the failure domain from UI. Only name, replica and compression
Setting target release to the active development branch (4.7.0). For any fixes, where required and requested, cloned BZs will be created for those release maintenance streams where appropriate once they are identified.
*** Bug 1897659 has been marked as a duplicate of this bug. ***
Assigning it to Gowtham as he is currently working on it
Failure domain now is setup to rack: spec: compressionMode: aggressive deviceClass: hdd erasureCoded: codingChunks: 0 dataChunks: 0 failureDomain: rack mirroring: {} parameters: compression_mode: aggressive quotas: {} replicated: size: 3 statusCheck: mirror: {} status: phase: Ready Verified on ocs 4.8.0-374.ci
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438