Bug 2028821 - Misspelled label in ODF management UI - MCG performance view
Summary: Misspelled label in ODF management UI - MCG performance view
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: All
OS: All
Target Milestone: ---
: 4.11.0
Assignee: Rishabh Bhandari
QA Contact: avdhoot
Depends On:
TreeView+ depends on / blocked
Reported: 2021-12-03 13:31 UTC by Dirk Haubenreisser
Modified: 2022-08-10 10:40 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:40:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
Screenshot (24.79 KB, image/png)
2021-12-03 13:31 UTC, Dirk Haubenreisser
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11047 0 None open Bug 2028821: Misspelled label in ODF management UI 2022-02-14 16:27:30 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:40:47 UTC

Description Dirk Haubenreisser 2021-12-03 13:31:31 UTC
Created attachment 1844591 [details]

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

The label 'Logical used Capacity' in the MCG performance view (dropdown 'I/O Operations') of the ODF console is misspelled. See attached screenshot.

Version of all relevant components (if applicable):

OCP 4.9.8
ODF 4.9.0

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. In the ODF console navigate to 'Storage -> OpenShift Data Foundation -> Overview -> <storage cluster> -> Object'
2. Go to 'Performance' card, select 'Multicloud Object Gateway'
3. Click on the dropdown labeled 'I/O Operations'
4. Observe menu entries in section 'Metric'

Actual results:

Menu item label says 'Logial used Capacity'.

Expected results:

Menu item label should say 'Logical used Capacity'.

Additional info:


Comment 6 avdhoot 2022-03-29 12:26:42 UTC
Need info about version of OCP and ODF in which bug is fixed or need to verify.

Comment 7 Mudit Agarwal 2022-03-29 14:39:13 UTC
This was fixed long back in ODF4.10, you can test with the latest 4.10 builds.

Comment 8 Dirk Haubenreisser 2022-03-30 12:37:44 UTC
Verified with ODF 4.10 build 210.

Comment 9 avdhoot 2022-04-01 10:15:48 UTC
Hi @dirk 

Can you please tell which OCp version you used while veryfying.

Because I am facing below issue when I used OCP-4.11 and ODF- 4.10 build 210.

Comment 10 Dirk Haubenreisser 2022-04-04 09:00:29 UTC
@avdhoot Be careful who you are sending email notification to - not sure who received this mail (if at all) but my email address certainly isn't "dirkAThausundgrundleonberg.de"

I have verified the fix for this UI labelling bug with ODF 4.10 build 210 running on OCP 4.10.5 (s390x).

Comment 12 avdhoot 2022-04-05 10:30:57 UTC
expected result seen on odf console. PFA for reference.

Hence marking the bug as verified

 OCP 4.11 (4.11.0-0.nightly-2022-03-29-152521) + ODF-4.11

Steps Used to verify-

1. Created cluster of OCP 4.11 + ODF 4.11
2. In the ODF console navigate to 'Storage -> OpenShift Data Foundation -> Overview -> <storage cluster> -> Object'
   Due to bug https://bugzilla.redhat.com/show_bug.cgi?id=2070542 , Directly jumped to overview page.

3. Go to 'Performance' card, select 'Multicloud Object Gateway'
4. Click on the dropdown labeled 'I/O Operations'
5. Observe menu entries in section 'Metric'

Comment 15 errata-xmlrpc 2022-08-10 10:40:31 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: OpenShift Container Platform 4.11.0 bug fix and security 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.


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