Bug 1824389 - Incorrect storage capacity view
Summary: Incorrect storage capacity view
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: management-console
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nishanth Thomas
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-16 05:23 UTC by palshure
Modified: 2023-09-07 22:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-20 09:54:44 UTC
Embargoed:
palshure: needinfo-


Attachments (Terms of Use)
console view (216.14 KB, image/png)
2020-04-16 05:23 UTC, palshure
no flags Details

Description palshure 2020-04-16 05:23:40 UTC
Created attachment 1679219 [details]
console view

Description of problem (please be detailed as possible and provide log
snippests):

The customer is not able to get the storage capacity view as explained in the "verification steps" in the following Red Hat 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

Attached the customer's current view and it is showing that they have a usable 12TiB which is not correct. It should show 4TiB available for their application. Initially they started with 2TiB and then scaled it to 4TiB.


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)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:


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