Bug #21607: rgw: s3 v4 auth fails teuthology s3-tests: test_object_header_acl_grants test_bucket_header_acl_grants - rgw - Ceph

Actions

Copy link

Bug #21607

open

rgw: s3 v4 auth fails teuthology s3-tests: test_object_header_acl_grants test_bucket_header_acl_grants

Added by Marcus Watts over 6 years ago. Updated almost 3 years ago.

Status:

Fix Under Review

Priority:

Normal

Assignee:

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

Ceph - v13.0.0

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

When running teuthology s3-tests with the environment variable "S3_USE_SIGV4=1", awsv4 signatures are enabled.

When this is done, these tests fail:
ERROR: s3tests.functional.test_s3.test_object_header_acl_grants
ERROR: s3tests.functional.test_s3.test_bucket_header_acl_grants

This fails doing awsv4 signatures, and the exact error appears to be in the sort order of "x-amz-grant-read-acp" vs. "x-amz-grant-read", "x-amz-grant-write-acp" vs. "x-amz-grant-write". It appears that the expected behavior is to sort the entire header line (which includes a ":" which sorts after "-", and not just the field name.

This behavior appers in both jewel and master.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Casey Bodley over 6 years ago

Related to Bug #21832: boto3 v4 SignatureDoesNotMatch failure due to sorting of sse-kms headers added

Actions

Copy link

Updated by Casey Bodley over 6 years ago

This appears to be a boto2 client bug, as reported in https://github.com/boto/boto/pull/3032.

Actions

Copy link

Updated by Ken Dreyer over 6 years ago

Status changed from New to 15
Backport deleted (~~jewel, luminous~~)

Unmarking this for backporting.

To be clear: the original RGW commit at https://github.com/ceph/ceph/pull/18046 was wrong, and we reverted this in #21832 . Please don't cherry-pick this PR anywhere :)

Actions

Copy link