Bug 1947796

Summary:	[GSS] Noobaa is creating many buckets on a single obc request from quay operator.
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Priya Pandey <prpandey>
Component:	Multi-Cloud Object Gateway	Assignee:	Evgeniy Belyi <ebelyi>
Status:	CLOSED ERRATA	QA Contact:	Parikshith <pbyregow>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	assingh, dzaken, ebelyi, ebenahar, etamir, muagarwa, nbecker, ocs-bugs, olakra, tdesala, tomckay
Target Milestone:	---	Flags:	prpandey: needinfo-
Target Release:	OCS 4.8.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	v4.8.0-386.ci	Doc Type:	Bug Fix
Doc Text:	.Buckets are always deleted when cleanup is required by the library Previously, on OBC creation failure, lib-bucket-provisioner sent a delete request to the provisioner for cleanup purposes before retrying. Noobaa provisioner would look at the reclaim policy of the object bucket but in some cases did not delete the underlying bucket. With this update, on cleanup scenarios, the underlying bucket should have been deleted regardless of the reclaim policy.	Story Points:	---
Clone Of:
Clones:	1959331 (view as bug list)		Environment:
Last Closed:	2021-08-03 18:15:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1959331, 1959333

Description Priya Pandey 2021-04-09 09:36:59 UTC

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)?

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

Comment 7 Danny 2021-04-20 08:38:59 UTC

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

Comment 21 Olive Lakra 2021-07-09 04:41:14 UTC

@mudit - please review the revised doc text and share feedback.

Comment 26 errata-xmlrpc 2021-08-03 18:15:56 UTC

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