Bug 2166572 - [CEE/sd][ceph-rgw][Unable to rename large objects using aws cli or s3cmd after upgrading to RHCS 5.3]
Summary: [CEE/sd][ceph-rgw][Unable to rename large objects using aws cli or s3cmd afte...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 5.3
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 6.0
Assignee: Pritha Srivastava
QA Contact: Chaithra
Akash Raj
URL:
Whiteboard:
Depends On: 2165890
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-02 08:19 UTC by Pritha Srivastava
Modified: 2023-09-19 04:33 UTC (History)
11 users (show)

Fixed In Version: ceph-17.2.5-65.el9cp
Doc Type: Bug Fix
Doc Text:
.Renaming large objects no longer fails when using temporary credentials returned by STS Previously, due to incorrect permission evaluation of `iam` policies while renaming large objects, renaming large objects would fail when temporary credentials returned by STS were used. With this fix, `iam` policies are correctly evaluated when temporary credentials returned by STS are used to rename large objects.
Clone Of: 2165890
Environment:
Last Closed: 2023-03-20 19:00:36 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6065 0 None None None 2023-02-02 08:22:28 UTC
Red Hat Product Errata RHBA-2023:1360 0 None None None 2023-03-20 19:00:51 UTC

Comment 7 errata-xmlrpc 2023-03-20 19:00:36 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 6.0 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-2023:1360
Comment 8 Red Hat Bugzilla 2023-09-19 04:33:12 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.