Bug 2232608 - [UI] [4.14] Wrong measurement unit. Topology. Resources. Observe.
Summary: [UI] [4.14] Wrong measurement unit. Topology. Resources. Observe.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.14.0
Assignee: Timothy Asir
QA Contact: Daniel Osypenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 14:06 UTC by Daniel Osypenko
Modified: 2023-11-08 18:55 UTC (History)
4 users (show)

Fixed In Version: 4.14.0-123
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 18:54:15 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 1011 0 None Merged Fix wrong measurement unit in Receive bandwidth graph 2023-08-29 15:20:34 UTC
Github red-hat-storage odf-console pull 1012 0 None Merged Bug 2232608: [release-4.14] Fix wrong measurement unit in Receive bandwidth graph 2023-09-05 08:08:42 UTC
Github red-hat-storage odf-console pull 1013 0 None Merged Bug 2232608: [release-4.14-compatibility] Fix wrong measurement unit in Receive bandwidth graph 2023-09-05 08:08:44 UTC
Red Hat Product Errata RHSA-2023:6832 0 None None None 2023-11-08 18:55:04 UTC

Description Daniel Osypenko 2023-08-17 14:06:39 UTC
Created attachment 1983828 [details]
wrong-utilizaton-units

Description of problem (please be detailed as possible and provide log
snippests):
 When navigating to Storage / Data Foundation / Topology / Observe the Receive bandwidth units in the graph shows PiB instead of KiB, see attachment
If Overall Receive bandwidth  measured in KiB, graph cannot show PiB units

Version of all relevant components (if applicable):

OC version:
Client Version: 4.13.4
Kustomize Version: v4.5.7
Server Version: 4.14.0-0.nightly-2023-08-11-055332
Kubernetes Version: v1.27.4+deb2c60

OCS verison:
ocs-operator.v4.14.0-110.stable              OpenShift Container Storage   4.14.0-110.stable              Succeeded

Cluster version
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.0-0.nightly-2023-08-11-055332   True        False         16h     Cluster version is 4.14.0-0.nightly-2023-08-11-055332

Rook version:
rook: v4.14.0-0.2d8264501d13c4389310b7fe2bab06bf060916d2
go: go1.20.5


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

no

Is there any workaround available to the best of your knowledge?

no

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:
new feature

Steps to Reproduce:
1. Deploy cluster OCP 4.14, ODF 4.14, login to management-console
2. Select any deployment from any node
3. Navigate to Storage / Data Foundation / Topology / "Observe" in sidebar and scroll down to Receive bandwidth 


Actual results:
Receive bandwidth measured in PiB on graph even though There are approx 1125,899,906,842.62 KiB in one PiB (Pebibyte) but on the graph on the screenshot it is like 0.25 PiB used at last measurement.

Expected results:
Receive bandwidth measured in proper units. If Overall Receive bandwidth  measured in KiB or any other proper unit.


Additional info:

Comment 8 errata-xmlrpc 2023-11-08 18:54:15 UTC
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 (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), 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/RHSA-2023:6832


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