Bug 1588731
| Summary: | Bucket lifecycles stick around after buckets are deleted | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Orit Wasserman <owasserm> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | medium | Docs Contact: | Erin Donnelly <edonnell> |
| Priority: | medium | ||
| Version: | 3.0 | CC: | anharris, cbodley, ceph-eng-bugs, edonnell, igreen, kbader, kdreyer, kjosy, mbenjamin, pasik, sweil, tchandra |
| Target Milestone: | z1 | Keywords: | TestOnly |
| Target Release: | 3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.8-3.el7cp Ubuntu: ceph_12.2.8-3redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
.Stale lifecycle configuration data of deleted buckets no longer persists in `OMAP` consuming space
Previously, in the Ceph Object Gateway (RGW), incorrect key formatting in the `RGWDeleteLC::execute()`function caused bucket lifecycle configuration metadata to persist after the deletion of the corresponding bucket. This caused stale lifecycle configuration data to persist in `OMAP` consuming space. With this update, the correct name for the lifecycle object is now used in `RGWDeleteLC::execute()`, and the lifecycle configuration is removed as expected on removal of the corresponding bucket.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-07 15:50:55 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: | 1629656 | ||
|
Description
Orit Wasserman
2018-06-07 18:41:56 UTC
Hi Matt, When we were testing bucket lifecycle policies related to a case opened by a customer, we hit the same bug. As far as I understand this bug is resolved and backported in Upstream. Can you let me know when this will be available in downstream? 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, 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-2019:0475 |