Bug 2345560 - Unable to Delete Objects when RADOS Pool quota hits Max [NEEDINFO]
Summary: Unable to Delete Objects when RADOS Pool quota hits Max
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 8.0z3
Assignee: Matt Benjamin (redhat)
QA Contact: Vidushi Mishra
Rivka Pollack
URL:
Whiteboard:
Depends On: 2342928
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-13 14:59 UTC by Matt Benjamin (redhat)
Modified: 2025-04-07 15:26 UTC (History)
13 users (show)

Fixed In Version: ceph-19.2.0-100.el9cp
Doc Type: Bug Fix
Doc Text:
.Ceph Object Gateway can now delete objects when RADOS is at maximum pool capacity Previously, when a RADOS pool was near its maximum quota, the Ceph Object Gateway was not able to delete objects. With this fix, Ceph Object Gateway can delete objects even when RADOS has reached its maximum pool threshold.
Clone Of: 2342928
Environment:
Last Closed: 2025-04-07 15:26:22 UTC
Embargoed:
vimishra: needinfo? (mbenjamin)
vimishra: needinfo? (cbodley)
rpollack: needinfo? (mbenjamin)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-10618 0 None None None 2025-02-13 15:01:17 UTC
Red Hat Product Errata RHSA-2025:3635 0 None None None 2025-04-07 15:26:25 UTC

Description Matt Benjamin (redhat) 2025-02-13 14:59:27 UTC
+++ This bug was initially created as a clone of Bug #2342928 +++

Comment 10 errata-xmlrpc 2025-04-07 15:26:22 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 (Important: Red Hat Ceph Storage 8.0 security, bug fix, and enhancement updates), 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/RHSA-2025:3635


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