Description of problem (please be detailed as possible and provide log snippests): - Also, it was observed that noobaa creates a large no. of empty buckets for a single OBC request from the quay registry. - The OBC requested by the quay registry stays in the Pending state although the OB is successfully created and in a Bounded state. Version of all relevant components (if applicable): OCS v4.6.3 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? - CU has tried installing Quay multiple times which resulted in the creation of 8262 buckets and ultimately noobaa-backing store went to rejected phase. Is there any workaround available to the best of your knowledge? N/A Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 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: N/A Steps to Reproduce: 1. Install the quay operator 2. Create the quay-registry instance 3. Verify teh status of OBC and OB. OBC will be in a Pending state. 4. Check the noobaa dashboard and bucket tab, a list of buckets will be created. Actual results: Noobaa created many 0B buckets for single OBC request and OBC stuck in Pending state. Expected results: Noobaa should create only one bucket for OB and OBC should be in a Bounded state. Additional info: In the nest comments
Hi Priya, is the bucket creation loop continue infinitely, or did it stop eventually? Also, did the backing store reach a ready state or is it always rejected? Thanks
@mudit - please review the revised doc text and share feedback.
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 Container Storage 4.8.0 container images bug fix and enhancement 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-2021:3003