Bug 2004366 - [UI][External Mode] Missing items under Utilization section in Block and File Overview page
Summary: [UI][External Mode] Missing items under Utilization section in Block and File...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nishanth Thomas
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-15 06:49 UTC by Jilju Joy
Modified: 2023-08-09 16:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-15 07:31:14 UTC
Embargoed:


Attachments (Terms of Use)
external mode screen shot (136.27 KB, image/png)
2021-09-15 06:49 UTC, Jilju Joy
no flags Details

Description Jilju Joy 2021-09-15 06:49:41 UTC
Created attachment 1823187 [details]
external mode screen shot

Description of problem (please be detailed as possible and provide log
snippests):
In an external mode cluster, only the "Used Capacity" and "Requested capacity" are available under the "Utilization" section of the "Block and File" "Overview" page.

Screen shot from both the external and internal mode cluster are attached for reference. The resource under the "Utilization" should match in both internal mode and external mode cluster.


$ oc get storagecluster
NAME                          AGE   PHASE   EXTERNAL   CREATED AT             VERSION
ocs-external-storagecluster   40h   Ready   true       2021-09-13T14:03:54Z   4.9.0

$ oc get storagesystem 
NAME                                        STORAGE-SYSTEM-KIND                  STORAGE-SYSTEM-NAME
ocs-external-storagecluster-storagesystem   storagecluster.ocs.openshift.io/v1   ocs-external-storagecluster

Storage system  conditions:
status:
    conditions:
    - lastHeartbeatTime: "2021-09-13T14:03:55Z"
      lastTransitionTime: "2021-09-13T14:03:55Z"
      message: Reconcile is completed successfully
      reason: ReconcileCompleted
      status: "True"
      type: Available
    - lastHeartbeatTime: "2021-09-13T14:03:55Z"
      lastTransitionTime: "2021-09-13T14:03:55Z"
      message: Reconcile is completed successfully
      reason: ReconcileCompleted
      status: "False"
      type: Progressing
    - lastHeartbeatTime: "2021-09-13T14:03:54Z"
      lastTransitionTime: "2021-09-13T14:03:54Z"
      message: StorageSystem CR is valid
      reason: Valid
      status: "False"
      type: StorageSystemInvalid
    - lastHeartbeatTime: "2021-09-13T14:03:55Z"
      lastTransitionTime: "2021-09-13T14:03:55Z"
      reason: Ready
      status: "True"
      type: VendorCsvReady
    - lastHeartbeatTime: "2021-09-13T14:03:55Z"
      lastTransitionTime: "2021-09-13T14:03:55Z"
      reason: Found
      status: "True"
      type: VendorSystemPresent


===============================================================================

Version of all relevant components (if applicable):
OCP 4.9.0-0.nightly-2021-09-10-170926
odf-operator.v4.9.0-132.ci

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?
Reporting the first occurance

Can this issue reproduce from the UI?
UI issue

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


Steps to Reproduce:
1. Install ODF external mode cluster.
2. Go to Storage --> OpehShift Data Foundation --> Select Storage Systems tab --> Select the storage system
3. Check the "Utilization" section in the "Block and File" "Overview" page.


Actual results:
Only the "Used Capacity" and "Requested capacity" are present.

Expected results:
Used Capacity
IOPS
Latency
Throughput
Recovery

Additional info:

Comment 3 Bipul Adhikari 2021-09-15 07:31:14 UTC
Closing this as this is how it is supposed to look.


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