Bug 2187654 - Noobaa buckets not deleting objects as per Lifecycle settings [NEEDINFO]
Summary: Noobaa buckets not deleting objects as per Lifecycle settings
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-18 10:56 UTC by Bipin Kunal
Modified: 2023-08-09 16:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-18 11:24:53 UTC
Embargoed:
bkunal: needinfo? (usrivast)


Attachments (Terms of Use)

Description Bipin Kunal 2023-04-18 10:56:30 UTC
Description of problem (please be detailed as possible and provide log
snippests):

We have been trying to use the S3 Lifecycle bucket cleardown to clean backups from the S3 bucket they are stored in, but with an expiry of one day nothing ever gets deleted:


nbcore=# SELECT data->>'_id', data->>'name', data->>'lifecycle_configuration_rules' FROM buckets WHERE data ? 'lifecycle_configuration_rules';
         ?column?         |                           ?column?                            |                                             ?column?

--------------------------+---------------------------------------------------------------+-------------------------------------------------------
--------------------------------------------
 642d4315cc3cba002932d70c | backups-xteams-core-prod-66944efe-5116-4f24-ae61-a8fe0eb0c7f8 | [{"id": "bucket-tidy", "filter": {"prefix": ""}, "stat
us": "Enabled", "expiration": {"days": 1}}]
(1 row)



Version of all relevant components (if applicable):

ODF-4.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

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

Additional Info:

https://issues.redhat.com/browse/RHSTOR-4483


Note You need to log in before you can comment on or make changes to this bug.