Description of problem (please be detailed as possible and provide log snippests): Object storage in a degraded state and customer is unable to access the buckets using "s3" command. When I checked noobaa-default-bucket-class is in rejected state its using backingstore noobaa-pv-backing-store, which is in "ALL_NODES_OFFLINE" state , This backingstore is created on rbd PV and that PV looks good History of the issue: Cluster becomes full(above 80%) so we deleted the unwanted PV's to get the free space after this, issue with object storage started. Version of all relevant components (if applicable): odf-operator.v4.11.5 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? yes, unable to access the object storage. Is there any workaround available to the best of your knowledge? No Can this issue reproducible? not sure Additional info: Latest ODF mustgather in supportshell path: /cases/03468361/0050-must-gather-odf-24032023.tar.gz.gz
Is there any update to this case?
Verified with ODF 4.13 build 4.13.0-186, increase noobaa pods resources, then upload and list 1M objects without any issues. Delete obc and backingstore are successfully. $ oc get storagecluster -n openshift-storage ocs-storagecluster -oyaml | yq '.spec.resources' mgr: limits: cpu: "3" memory: 3Gi requests: cpu: "3" memory: 3Gi noobaa-core: limits: cpu: "3" memory: 4Gi requests: cpu: "3" memory: 4Gi noobaa-db: limits: cpu: "3" memory: 4Gi requests: cpu: "3" memory: 4Gi noobaa-endpoint: limits: cpu: "3" memory: 4Gi requests: cpu: "3" memory: 4Gi
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.13.0 enhancement and 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-2023:3742