Bug 2187654
| Summary: | Noobaa buckets not deleting objects as per Lifecycle settings | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Bipin Kunal <bkunal> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> |
| Status: | CLOSED WONTFIX | QA Contact: | krishnaram Karthick <kramdoss> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.11 | CC: | ocs-bugs, odf-bz-bot, usrivast |
| Target Milestone: | --- | Flags: | bkunal:
needinfo?
(usrivast) |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-04-18 11:24:53 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: | |||
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