Project

General

Profile

Actions

Bug #52799

closed

Segmentation Fault in radosgw-admin period update --commit

Added by Stefan Schueffler over 2 years ago. Updated over 2 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

On one of our ceph clusters it is not possible to set up a simple radosgw/S3 basic setup. The cluster was running fine for several months including a working S3 setup. While exploring new ceph features like multisite S3/sync, we decided to recreate S3 from scratch. Now, it is not possible to setup even the most simple S3 setup.

I deleted all radosgw-related pools (the .rgw.root pool as well as the corresponding log, meta, index, control, and so on),
deleted all zones, zonegroups, realms, periods,
and then tried to create a simple new realm, a simple zonegroup, an simple zone, (radosgw-admin create ... works fine),
and then when doing the "radosgw-admin period update --commit" it always failes with segmentation fault.

In attached file "commands" there are the commands to create the fresh installation,
in "cephadm.log" there is the radosgw-admin period update including the debug log.

I would be happy to provide further log / debug if necessary.


Files

commands (4.96 KB) commands commands to create the empty fresh S3 installation Stefan Schueffler, 10/01/2021 10:32 AM
cephadm.log (491 KB) cephadm.log log file including the segmentation fault. Stefan Schueffler, 10/01/2021 10:33 AM

Related issues 1 (0 open1 closed)

Is duplicate of rgw - Bug #52900: segfault on FIPS enabled server as result of EVP_md5 disabled in opensslResolvedMark Kogan

Actions
Actions #1

Updated by Greg Farnum over 2 years ago

  • Project changed from Ceph to rgw
Actions #2

Updated by Casey Bodley over 2 years ago

we've seen a similar crash from `radosgw-admin period update --commit` inside of openssl due to FIPS enforcement. is FIPS enabled here?

Actions #3

Updated by Stefan Schueffler over 2 years ago

Yes, FIPS is enabled.

I just tested this right now with FIPS disabled - and... it works.

So, i have a work-a-round to get the config back to a running working cluster (temporarily disable FIPS-mode, reboot the nodes), but we need to (re-)enable FIPS-mode due to customer requirements.

Actions #4

Updated by Casey Bodley over 2 years ago

  • Is duplicate of Bug #52900: segfault on FIPS enabled server as result of EVP_md5 disabled in openssl added
Actions #5

Updated by Casey Bodley over 2 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF