Bug 1824882
| Summary: | [GSS][vsphere] Scaling OCS4 on a different StorageClass is not reflected correclty | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Feras Al Taher <faltahe> |
| Component: | management-console | Assignee: | Nishanth Thomas <nthomas> |
| Status: | CLOSED DUPLICATE | QA Contact: | Elad <ebenahar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2 | CC: | assingh, bkunal, dkochuka, hnallurv, jefbrown, madam, nthomas, ocs-bugs, ratamir |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-17 06:46:40 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: | |||
|
Description
Feras Al Taher
2020-04-16 15:37:21 UTC
Hey Bipin, I surprised that you closed this bug. First of all the documentation and public statement of ocs4.3 explain that you can choose different StroageClass. Can you please confirm that OCS4.3 work as expected. and this issue is fixed in OCS4.3. This is a BUG because the functionality does not work in OCS4.2. I advise you to first track if this bug got fixed or not in OCS4.3. because if it wasn't then you should at least block users from choosing a different storageclass in the OCS portal. The documentation https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.2/html-single/managing_openshift_container_storage/index#proc_scaling-up-storage-by-adding-capacity-to-your-openshift-container-storage-nodes_rhocs Clearly says to "From this dialog box, you can set the requested additional capacity and the storage class. The size should always be set in multiples of 2TiB. On AWS, the storage class should be set to gp2. On VMWare, the storage class should be set to thin." Based on this, selecting other storageclass other than thin or gp2 is not recommended The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |