Bug 1967901 - [RGW]: Crash on MS secondary when sync resumes post error
Summary: [RGW]: Crash on MS secondary when sync resumes post error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW-Multisite
Version: 4.2
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: 5.2
Assignee: Casey Bodley
QA Contact: Anuchaithra
Akash Raj
URL:
Whiteboard:
Depends On:
Blocks: 2079016 2102272
TreeView+ depends on / blocked
 
Reported: 2021-06-04 10:42 UTC by Tejas
Modified: 2023-09-15 01:34 UTC (History)
10 users (show)

Fixed In Version: ceph-16.2.8-17.el8cp
Doc Type: Bug Fix
Doc Text:
.Null pointer check no longer causes multi-site data sync crash Previously, a null pointer access would crash the multisite data sync. With this fix, null pointer check is successfully implemented, preventing any possible crashes.
Clone Of:
: 2079016 (view as bug list)
Environment:
Last Closed: 2022-08-09 17:35:53 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 49302 0 None None None 2022-04-22 16:35:02 UTC
Github ceph ceph pull 46007 0 None open rgw: RGWCoroutine::set_sleeping() checks for null stack 2022-04-22 16:35:02 UTC
Red Hat Issue Tracker RHCEPH-288 0 None None None 2021-09-02 18:45:40 UTC
Red Hat Product Errata RHSA-2022:5997 0 None None None 2022-08-09 17:36:25 UTC

Internal Links: 2009118

Comment 29 errata-xmlrpc 2022-08-09 17:35:53 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 Security, Bug Fix, and Enhancement 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:5997
Comment 31 Red Hat Bugzilla 2023-09-15 01:34:24 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days
Note You need to log in before you can comment on or make changes to this bug.