Created attachment 1924161 [details] Screenshot of storagesystem page Description of problem (please be detailed as possible and provide log snippests): Value of all the Fields (like Raw Capacity, Used Capacity, Latency etc.) in Storagesystem page shows 0 Version of all relevant components (if applicable): OCP version - 4.12 ODF version - 4.12 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)? 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: Steps to Reproduce: 1. Deploy ODF4.12 on OCP4.12 2. Login to Web console and Navigate to Storage -> Data Foundation 3. Now click on Storagesystems tab from navbar and check all the values for the storagesystem Actual results: It shows values as 0B for all the fields like Raw Capacity. Expected results: It should show actual capacity. Additional info:
Adding it back to QA. If it is still an issue, please re-open the BZ with steps. Thanks, Arun
(In reply to arun kumar mohan from comment #14) > Adding it back to QA. If it is still an issue, please re-open the BZ with > steps. > > Thanks, > Arun Hi Arun, IIUC, there is no fix (PR) done for this issue. You would like QE to retest it to see if the issue still persists based on the clarification you provided in comment 13. If yes, then ON_QA is not the right state. QE can retest and move it to closed state with resolution 'worksforme' if the issue is not reproduced. Could you please change the state to NEW/ASSIGNED? Regards, Harish
(In reply to Harish NV Rao from comment #16) > (In reply to arun kumar mohan from comment #14) > > Adding it back to QA. If it is still an issue, please re-open the BZ with > > steps. > > > > Thanks, > > Arun > > Hi Arun, > > IIUC, there is no fix (PR) done for this issue. You would like QE to retest > it to see if the issue still persists based on the clarification you > provided in comment 13. If yes, then ON_QA is not the right state. QE can > retest and move it to closed state with resolution 'worksforme' if the issue > is not reproduced. Could you please change the state to NEW/ASSIGNED? > > Regards, > Harish Arun, a gentle reminder ^^
Yes Harish, I want QE to retest it (as per comment#13) and check whether the issue is reproducible. Moving it to 'NEW' state.
I remember there was a PR (diff BZ) which fixed this issue. Arun if u want u can add that PR to the BZ and move to ON_QA.
Not a 4.13 blocker
On IBM Power cluster, In Storagesystem tab, all the fields still shows 0. ODF version: [root@rdr-odf-sc-lon06-bastion-0 ~]# oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-local-storage local-storage-operator.v4.14.0-202307211703 Local Storage 4.14.0-202307211703 Succeeded openshift-operator-lifecycle-manager packageserver Package Server 0.19.0 Succeeded openshift-storage mcg-operator.v4.14.0-113.stable NooBaa Operator 4.14.0-113.stable Succeeded openshift-storage ocs-operator.v4.14.0-113.stable OpenShift Container Storage 4.14.0-113.stable Succeeded openshift-storage odf-csi-addons-operator.v4.14.0-113.stable CSI Addons 4.14.0-113.stable Succeeded openshift-storage odf-operator.v4.14.0-113.stable OpenShift Data Foundation 4.14.0-113.stable Succeeded [root@rdr-odf-sc-lon06-bastion-0 ~]# oc version Client Version: 4.14.0-ec.4 Kustomize Version: v5.0.1 Server Version: 4.14.0-ec.4 Kubernetes Version: v1.27.3+4aaeaec [root@rdr-odf-sc-lon06-bastion-0 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.14.0-ec.4 True False 2d Cluster version is 4.14.0-ec.4 Attaching the screenshot as well. name of the attachment-> storagesystem-capacity-missing-odf414
While in the cluster where ODF version is [root@rdr-odftest-lon06-bastion-0 ~]# oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-local-storage local-storage-operator.v4.14.0-202307211703 Local Storage 4.14.0-202307211703 Succeeded openshift-operator-lifecycle-manager packageserver Package Server 0.19.0 Succeeded openshift-storage mcg-operator.v4.14.0-99.stable NooBaa Operator 4.14.0-99.stable Succeeded openshift-storage ocs-operator.v4.14.0-99.stable OpenShift Container Storage 4.14.0-99.stable Succeeded openshift-storage odf-csi-addons-operator.v4.14.0-99.stable CSI Addons 4.14.0-99.stable Succeeded openshift-storage odf-operator.v4.14.0-99.stable OpenShift Data Foundation 4.14.0-99.stable Succeeded OC version: [root@rdr-odftest-lon06-bastion-0 ~]# oc version Client Version: 4.14.0-ec.4 Kustomize Version: v5.0.1 Server Version: 4.14.0-ec.4 Kubernetes Version: v1.27.3+4aaeaec All the capacities are getting populated. Attaching the screenshot.
Moving the bug to verified based on the above comment.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days