Project

General

Profile

Actions
Copy link

Backport #53647

closed

octopus: assumed-role: s3api head-object returns 403 Forbidden, even if role has ListBucket, for non-existent object, patch in https://tracker.ceph.com/issues/49780 inconsistent with AWS

Added by Backport Bot over 2 years ago. Updated about 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Release:
octopus
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Related issues 1 (0 open — 1 closed)

Copied from rgw - Bug #52302: assumed-role: s3api head-object returns 403 Forbidden, even if role has ListBucket, for non-existent object, patch in https://tracker.ceph.com/issues/49780 inconsistent with AWSResolvedPritha Srivastava

Actions
Actions
Copy link
 #1

Updated by Backport Bot over 2 years ago

  • Copied from Bug #52302: assumed-role: s3api head-object returns 403 Forbidden, even if role has ListBucket, for non-existent object, patch in https://tracker.ceph.com/issues/49780 inconsistent with AWS added
Actions
Copy link
 #2

Updated by Konstantin Shalygin about 1 year ago

  • Status changed from New to Rejected

Octopus is EOL

Actions
Copy link

Also available in: Atom PDF