Bug 1887849

Summary:	When creating new storage class failure_domain is missing.
Product:	OpenShift Container Platform	Reporter:	Shay Rozen <srozen>
Component:	Console Storage Plugin	Assignee:	gowtham <gshanmug>
Status:	CLOSED ERRATA	QA Contact:	Elad <ebenahar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	afrahman, aos-bugs, assingh, jefbrown, jelopez, madam, nthomas, ocs-bugs, scuppett
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1953606 (view as bug list)		Environment:
Last Closed:	2021-07-27 22:33:41 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:	1953606

Description Shay Rozen 2020-10-13 13:19:10 UTC

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:

Comment 2 Travis Nielsen 2020-10-13 13:47:27 UTC

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".

Comment 3 Shay Rozen 2020-10-13 14:31:12 UTC

There is no way to input the failure domain from UI. Only name, replica and compression

Comment 4 Stephen Cuppett 2020-10-15 13:51:51 UTC

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.

Comment 5 Kanika Murarka 2020-11-16 11:41:36 UTC

*** Bug 1897659 has been marked as a duplicate of this bug. ***

Comment 9 Vineet 2021-03-24 05:30:22 UTC

Assigning it to Gowtham as he is currently working on it

Comment 11 Shay Rozen 2021-05-11 07:31:37 UTC

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

Comment 14 errata-xmlrpc 2021-07-27 22:33:41 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 (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