Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2416754

Summary: [RGW] Observing 403 error for multi-part request while other requests like ‘cp’ etc are working fine
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Bipin Kunal <bkunal>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED UPSTREAM QA Contact: Hemanth Sai <hmaheswa>
Severity: urgent Docs Contact: Rivka Pollack <rpollack>
Priority: unspecified    
Version: 8.1CC: bkunal, cbodley, ceph-eng-bugs, cephqe-warriors, ckulal, hmaheswa, kjosy, mbenjamin, mkasturi, pdhange, prsrivas, rpollack, sbaldwin, shabhard, syeshwan, tserlin
Target Milestone: ---   
Target Release: 9.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-20.1.0-110 Doc Type: Bug Fix
Doc Text:
.Tenant user policy and role-based permissions now work as expected after upgrade Previously, some policy or role-based permissions involving legacy tenant users behaved differently after upgrading to releases that support IAM accounts. As a result, expected access grants would fail. With this fix, a configuration option has been introduced to allow backward compatibility with previous version behavior.
Story Points: ---
Clone Of: 2403635 Environment:
Last Closed: 2026-03-04 09:57:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2388233, 2403635    

Description Bipin Kunal 2025-11-24 14:26:51 UTC
+++ This bug was initially created as a clone of Bug #2403635 +++

Comment 9 Red Hat Bugzilla 2026-03-04 09:57:33 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.

Comment 10 Red Hat Bugzilla 2026-03-05 04:31:33 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days or the product is inactive and locked