Bug 2088601 - [RHCS][GSS][OCS 4.9] pod rook-ceph-rgw client.rgw.ocs.storagecluster.cephobjectstore.a crashed - thread_name:radosgw
Summary: [RHCS][GSS][OCS 4.9] pod rook-ceph-rgw client.rgw.ocs.storagecluster.cephobj...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 5.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: 5.1z2
Assignee: Mark Kogan
QA Contact: Uday kurundwade
Akash Raj
URL:
Whiteboard:
Depends On: 2088571
Blocks: 2086724 2099589 2101297
TreeView+ depends on / blocked
 
Reported: 2022-05-19 19:06 UTC by Vikhyat Umrao
Modified: 2022-06-30 20:55 UTC (History)
20 users (show)

Fixed In Version: ceph-16.2.7-114.el8cp
Doc Type: Bug Fix
Doc Text:
.Usage of MD5 for non-cryptographic purposes in a FIPS environment is allowed Previously, in a FIPS enabled environment, the usage of MD5 digest was not allowed by default, unless explicitly excluded for non-cryptographic purposes. Due to this, a segfault occurred during the S3 complete multipart upload operation. With this fix, the usage of MD5 for non-cryptographic purposes in a FIPS environment for S3 complete multipart `PUT` operations is explicitly allowed and the S3 multipart operations can be completed.
Clone Of: 2088571
Environment:
Last Closed: 2022-06-30 20:54:48 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-4339 0 None None None 2022-05-19 19:19:41 UTC
Red Hat Product Errata RHBA-2022:5450 0 None None None 2022-06-30 20:55:15 UTC

Comment 10 errata-xmlrpc 2022-06-30 20:54:48 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 (Red Hat Ceph Storage 5.1 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/RHBA-2022:5450
Note You need to log in before you can comment on or make changes to this bug.