Project

General

Profile

Actions
Copy link

Bug #48716

open

aws-s3 incompatibility related metadata

Added by Ilsoo Byun over 3 years ago. Updated over 1 year ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Ilsoo Byun
Target version:
Ceph - v17.0.0
% Done:

0%

Source:
Tags:
backport_processed
Backport:
octopus, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
38737
Crash signature (v1):
Crash signature (v2):

Description

When using metadata containing _, the behavior is different from aws-s3.

s3cmd put ~/1m s3://mytest --add-header 'x-amz-meta-key_1: value_1'
s3cmd get --debug s3://mytest/1m

rgw result:

{'headers': {
             ...
             'x-amz-meta-key6-1': 'value_1',
             ...

aws-s3 result:

{'headers': {
             ...
             'x-amz-meta-key6_1': 'value_1',
             ...

The second case is

s3cmd put ~/1m s3://mytest --add-header 'x_amz_meta_key_1: value_1'
s3cmd get --debug s3://mytest/1m

rgw result:

{'headers': {
             ...
             'x-amz-meta-key6-1': 'value_1',
             ...

aws-s3 result:

{'headers': {
             ...

Related issues 3 (1 open — 2 closed)

Related to rgw - Bug #51772: tempest failures: test_create_container_with_remove_metadata_key/valuePending BackportAli Maredia

Actions
Copied to rgw - Backport #52285: octopus: aws-s3 incompatibility related metadataRejectedActions
Copied to rgw - Backport #52286: pacific: aws-s3 incompatibility related metadataResolvedCory SnyderActions
Actions
Copy link
 #2

Updated by J. Eric Ivancich about 3 years ago

  • Pull request ID set to 38737
Actions
Copy link
 #3

Updated by J. Eric Ivancich about 3 years ago

  • Status changed from New to Resolved
  • Assignee set to Ilsoo Byun
  • Target version set to v17.0.0

This looks to me like something that should be backported to nautilus (near end-of-life), octopus, and pacific. Any objection?

Actions
Copy link
 #4

Updated by J. Eric Ivancich over 2 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to octopus, pacific

This looks like a bug fix that needs backports.

Also, rather than re-implementing the same algorithm 3 separate times, I think a function that could be called from all these places would have removed some technical debt.

Actions
Copy link
 #5

Updated by Backport Bot over 2 years ago

  • Copied to Backport #52285: octopus: aws-s3 incompatibility related metadata added
Actions
Copy link
 #6

Updated by Backport Bot over 2 years ago

  • Copied to Backport #52286: pacific: aws-s3 incompatibility related metadata added
Actions
Copy link
 #7

Updated by Casey Bodley over 2 years ago

  • Related to Bug #51772: tempest failures: test_create_container_with_remove_metadata_key/value added
Actions
Copy link
 #8

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions
Copy link

Also available in: Atom PDF