Moving it to ocs as it is fixed there.
The PR is still under review: https://github.com/red-hat-storage/ocs-operator/pull/1761 Moving this out of 4.11.2
OCS-Operator PR is merged: https://github.com/red-hat-storage/ocs-operator/pull/1761 and Mudit has backported it to the previous builds
As observed in the original BZ's comment: https://bugzilla.redhat.com/show_bug.cgi?id=2026144#c20 , the TWO graphs will never match, because the Overview page shows the map representing the sum of Read+Writes whereas the StorageSystem's Utilization card shows separate/individual maps of Read and Write. So these maps will never match. What we have done is, to make the queries and collection intervals same.
The new issue is seen on build 4.11.3-5. 1. ODF Overview page: - Performance card IOPs, Latency and Throughput datas are empty 2. ODF StorageSystems Details page -> Utilization card: IOPS and Throughput data are showing correct except Latency which currently shows "Not available". 3. Data Foundation -> Storage Systems tab: Data are showing empty as well See attached for more detail. This is blocking the verification of this BZ.
PR created: https://github.com/red-hat-storage/ocs-operator/pull/1885 , for 4.11 branch. @Sunil, please take a look
Observed IOPS, Latency, Throughput and Used Capacity values in Performance card are closely matching with StorageSystems Block and File card. Verified in version $ oc get csv -n openshift-storage NAME DISPLAY VERSION REPLACES PHASE mcg-operator.v4.11.4 NooBaa Operator 4.11.4 mcg-operator.v4.11.3 Succeeded ocs-operator.v4.11.4 OpenShift Container Storage 4.11.4 ocs-operator.v4.11.3 Succeeded odf-csi-addons-operator.v4.11.4 CSI Addons 4.11.4 odf-csi-addons-operator.v4.11.3 Succeeded odf-operator.v4.11.4 OpenShift Data Foundation 4.11.4 odf-operator.v4.11.3 Succeeded Note: 1. During this test ran some IO 2. Updated chart values for 24hrs in Performance and StorageSystems Block and File card 3. Took one specific time eg: 10.03 and gathered values for all mentioned params in 1st line 4. Values are not exact but its closely matching, even time is not exact its +/- 0.02 Moving the BZ to verified state
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 (Red Hat OpenShift Data Foundation 4.11.4 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/RHBA-2022:8877