Bug 2040099 - [Doc SCALING OUT STORAGE CAPACITY], Add capacity via UI on cluster with Flexible Scaling
Summary: [Doc SCALING OUT STORAGE CAPACITY], Add capacity via UI on cluster with Flexi...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Agil Antony
QA Contact: Oded
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 23:19 UTC by Oded
Modified: 2023-08-09 16:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2044337 (view as bug list)
Environment:
Last Closed: 2023-06-15 06:53:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Oded 2022-01-12 23:19:30 UTC
Describe the issue:
On LSO cluster with Flexible Scaling [OCP 4.8 and above], after clicking on "Add Capacity" button the Count param (storagecluster yaml file) increases by the number of PVs on Available state [X -> X+ PVs on Available]
According to the document there is no option to add Capacity via UI when flexible scaling is enabled 

Describe the task you were trying to accomplish:

Suggestions for improvement:

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html/scaling_storage/scaling-out-storage-capacity_rhodf#verifying-if-flexible-scaling-is-enabled_rhodf

Chapter/Section Number and Title:
3.2.2.2. Adding capacity using the YAML in multiples of 1 OSD

Product Version:
ODF4.9 and OCS4.8

Environment Details:
LSO cluster with Flexible Scaling

Any other versions of this document that also needs this update:
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.8/html/scaling_storage/scaling-out-storage-capacity_rhocs#adding-capacity-using-YAML-in-the-multiples-of-1-OSD_rhocs

Additional information:

Comment 14 krishnaram Karthick 2022-02-07 10:55:35 UTC
Discussed internally with Doc, QE and Bipin - we decided to Remove this bug from 4.9.3 so the change could be made to 4.10 first.


Note You need to log in before you can comment on or make changes to this bug.