Bug 2139258 - [cee/sd][rgw][crash] RGW instance getting crashed while performing the trim operation on non-existing bucket.
Summary: [cee/sd][rgw][crash] RGW instance getting crashed while performing the trim o...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW-Multisite
Version: 5.0
Hardware: x86_64
OS: All
high
high
Target Milestone: ---
: 5.3
Assignee: Matt Benjamin (redhat)
QA Contact: Madhavi Kasturi
Akash Raj
URL:
Whiteboard:
Depends On:
Blocks: 2126049
TreeView+ depends on / blocked
 
Reported: 2022-11-02 02:31 UTC by Kritik Sachdeva
Modified: 2023-09-19 04:29 UTC (History)
16 users (show)

Fixed In Version: ceph-16.2.10-68.el8cp
Doc Type: Bug Fix
Doc Text:
.Processes trimming retired bucket index entries no longer cause `radosgw` instance to crash Previously, under some circumstances, processes trimming retired bucket index entries could access an uninitialized pointer variable resulting in the `radosgw` instance to crash. With this fix, code is initialized immediately before use and the `radosgw` instance no longer crashes.
Clone Of:
Environment:
Last Closed: 2023-01-11 17:41:26 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 54119 0 None None None 2022-11-02 02:43:53 UTC
Red Hat Issue Tracker RHCEPH-5541 0 None None None 2022-11-02 03:07:38 UTC
Red Hat Product Errata RHSA-2023:0076 0 None None None 2023-01-11 17:42:18 UTC

Comment 38 errata-xmlrpc 2023-01-11 17:41:26 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.3 security update and Bug Fix), 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-2023:0076
Comment 39 Red Hat Bugzilla 2023-09-19 04:29:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.