Description of problem (please be detailed as possible and provide log snippests): When using 'Add Capacity' UI it could be nice if we can provide more information about used capacity / provisioned capacity and percentage occupied. Considering RBD and CephFS are using thin provisioning, we could advise total capacity provisioned for PVs despite percentage occupied is much less thanks to thin provisioning. Just to check the level of over-provisioning user is committing. Version of all relevant components (if applicable): OCS 4.2 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No, just more insights for user 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. Use "Add Capacity" dialog in the OpenShift UI 2. 3. Actual results: Used Capacity is the only information displayed Expected results: Used NET Capacity, Total RAW capacity, Total NET Capacity (dividing by replica 3), % occupation, Total NET provisioned in PVs Additional info: Important in all disk capacity measures to specify if it's RAW or NET
Created attachment 1654962 [details] New design providing more information The requested changes are made and pushed to ocp 4.4.
This bug is ON_QA, changing to ocs-4.3.0
Created attachment 1672743 [details] verification screenshot With a supported OSD size deployment, we get the details about the capacity and the raw capacity that will be used after extension. Please note that in case the OSD used is not from the supported size (0.5, 2, 4), then bug 1816169 is encountered.
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, 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/RHBA-2020:1437