Created attachment 1806738 [details] Dashboard warning Description of problem (please be detailed as possible and provide log snippests): After installing OCS operator using internal storage by disk. We see all PVs provisioned by LSO begin firing "The PersistentVolume claimed by ocs-deviceset-local-sc-0-data-10p5drg in Namespace openshift-storage is only 0% free." for each PersistentVolume. These PVs are empty and have never been bound to PVCs. Version of all relevant components (if applicable): OCP 4.8.2 OCS 4.8.0-456.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No, this is only a warning. I can continue to deploy new workloads on new persistent volumes. Is there any workaround available to the best of your knowledge? None was running at the initial time of this error. A fresh ocp cluster with fresh LSO and OCS operators installed. 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, we've seen this on each cluster we've provisioned. Steps to Reproduce: 1. Install ocp, lso, and ocs 2. Attach disk to cluster nodes and create LSO volumegroup to create PVs for each 3. Create ocs-storagecluster with option "Internal - Attached devices" set these LSO PVs as the attached devices. Actual results: In cluster overview page get warnings for each PV with 0% free message. Additional info: Must gather logs to follow
must-gather here -> https://drive.google.com/file/d/1wBLupr2JJ0VBKuO4lhVL9J0Yl65DbWdS/view?usp=sharing
Looks like a duplicate of BZ 973147
I don't have access there. But as long as people are aware of it. Thank you.
(In reply to Tom Dale from comment #4) > I don't have access there. But as long as people are aware of it. Thank you. Ah, I referenced a wrong BZ number (I dropped a 1st digit in the bz number). Also I removed the red hat group from the actual BZ, so that you can access it. The problem was identified in OCP, and it's going to be fixed in OCP 4.9 See BZ 1973147 *** This bug has been marked as a duplicate of bug 1973147 ***