Bug 1940813 - rgw-orphan-list tool consuming more space than expected 5.1
Summary: rgw-orphan-list tool consuming more space than expected 5.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW-Multisite
Version: 4.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: 5.1
Assignee: J. Eric Ivancich
QA Contact: Vidushi Mishra
Ranjini M N
URL:
Whiteboard:
Depends On:
Blocks: 2031073
TreeView+ depends on / blocked
 
Reported: 2021-03-19 09:27 UTC by Manjunatha
Modified: 2022-04-04 10:20 UTC (History)
14 users (show)

Fixed In Version: ceph-16.2.6-2.el8cp
Doc Type: Bug Fix
Doc Text:
.The `radosgw-admin bucket radoslist...` command with multipart upload entries in the bucket index works as expected Previously, the `radosgw-admin bucket radoslist...` command would get stuck in an infinite loop when there were more than 1000 incomplete multipart upload entries in the bucket index. With this release, the `radosgw-admin bucket radoslist ...` command does not get stuck when there are more than 1000 incomplete multipart upload entries in the bucket index and the tools that use the `radosgw-admin bucket radoslist...` command such as `rgw-orphan-list` and `rgw-gap-list` work as expected.
Clone Of:
Environment:
Last Closed: 2022-04-04 10:19:55 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:1174 0 None None None 2022-04-04 10:20:13 UTC

Comment 7 Manjunatha 2021-03-19 09:42:24 UTC 
02880115
Comment 60 errata-xmlrpc 2022-04-04 10:19:55 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 (Moderate: Red Hat Ceph Storage 5.1 Security, Enhancement, and Bug Fix 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/RHSA-2022:1174
Note You need to log in before you can comment on or make changes to this bug.