Bug 2344731 - rgw/cloud-restore: Do not send internal RGW headers to cloud-endpoint
Summary: rgw/cloud-restore: Do not send internal RGW headers to cloud-endpoint
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 8.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 8.1
Assignee: Soumya Koduri
QA Contact: Vidushi Mishra
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2351689
TreeView+ depends on / blocked
 
Reported: 2025-02-10 19:23 UTC by Soumya Koduri
Modified: 2025-06-04 17:54 UTC (History)
5 users (show)

Fixed In Version: ceph-19.2.1-60.el9cp
Doc Type: Bug Fix
Doc Text:
.Ceph Object Gateway internal HTTP headers are no longer sent while transitioning the object to Cloud Previously, some Ceph Object Gateway internal HTTP header values were sent to the Cloud endpoint, when transitioning the object to Cloud. As a result, some S3 cloud services did not recognize the headers and failed the transition or failed to restore the operation of the objects. With this fix, internal HTTP headers are not sent to Cloud and transitioning to Cloud works as expected.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-10585 0 None None None 2025-02-10 19:24:28 UTC

Description Soumya Koduri 2025-02-10 19:23:18 UTC 
Description of problem:

This is for the epic https://jsw.ibm.com/browse/ISCE-1472 

While validating cloud-restore feature with PoINT archival S3 gateway emulator, it was found that GET request fails with 403 error due to below reason -

Currently PAG does not alphabetically sort unknown query parameters before calculation the signature of the request. As a result the calculated signature differs from that the S3 client software has calculated before sending the request and this causes that the request is rejected.
<<
https://www.point.de/en/solutions/functions/cloud-and-object-storage-integration/

PAG server might fix this issue but meanwhile, since these headers are custom and internal to RGW, they are not needed and can be omitted while fetching object from external cloud-service.


Upstream tracker: https://tracker.ceph.com/issues/69238
PR :  https://github.com/ceph/ceph/pull/61090

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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