Bug 1834697 - [rgw] RGW daemon crash when setting up multisite
Summary: [rgw] RGW daemon crash when setting up multisite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW-Multisite
Version: 4.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: z1
: 4.1
Assignee: Mark Kogan
QA Contact: Tejas
URL:
Whiteboard:
: 1835444 (view as bug list)
Depends On:
Blocks: 1835846
TreeView+ depends on / blocked
 
Reported: 2020-05-12 09:14 UTC by Mark Kogan
Modified: 2020-07-20 14:21 UTC (History)
6 users (show)

Fixed In Version: ceph-14.2.8-61.el8cp, ceph-14.2.8-68.el7cp
Doc Type: Bug Fix
Doc Text:
Cause: During the setup process of a multisite environment a segmentation fault occured in primary zone rados gateway while the replicated zone was beeing configured. Consequence: The primary zone rados gateway was restarted by the systemd service and the multisite setup process would proceed. Fix: Modified the shutdown order of internal threads so that the race condition during threads shutdown would not occur. Result: The segmentation fault does not occur.
Clone Of:
: 1835846 (view as bug list)
Environment:
Last Closed: 2020-07-20 14:21:03 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 32927/commits/0f3e1f023a899f261bb38e7236ac35587438ad29 0 None None None 2020-09-11 06:02:34 UTC
Red Hat Product Errata RHSA-2020:3003 0 None None None 2020-07-20 14:21:28 UTC

Comment 4 Mark Kogan 2020-05-14 16:01:38 UTC
*** Bug 1835444 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2020-07-20 14:21:03 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, 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-2020:3003


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