Project

General

Profile

Actions
Copy link

Bug #67787

closed

rgw/storage class - copyobject should not inherit storage class

Added by Marcus Watts over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Raja Sharma
Target version:
-
% Done:

0%

Source:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
Released In:
Upkeep Timestamp:

Description

If ceph rgw copyobject is given a storage class, it correctly stores the new object with that class. If the storage class is not specified, it is set to the same storage class as the source object. I believe this is incorrect. According to the aws doc, if the storage class is not specified, it is set to 'STANDARD'.

ref,
https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html

Files

clipboard-202412120517-fwcvv.png (530 KB) clipboard-202412120517-fwcvv.png Raja Sharma, 12/12/2024 10:17 AM
Actions
Copy link
 #1

Updated by J. Eric Ivancich over 1 year ago

  • Assignee set to Marcus Watts
Actions
Copy link
 #2

Updated by Raja Sharma over 1 year ago

  • Assignee changed from Marcus Watts to Raja Sharma
Actions
Copy link
 #3

Updated by Raja Sharma about 1 year ago

Status Change: Closed

Validated with upstream main branch.

if ceph rgw copyobject is given a storage-class, it correctly stores new object with that storage-class.
And if there is no storage-class given, it correctly stores new object with STANDARD(according to AWS Doc https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html) not source storage-class.

So, Already fixed

Actions
Copy link
 #4

Updated by Raja Sharma about 1 year ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF