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