CI: update known failures for the ceph tests

Code Issues Proposed changes

For some reason, when we switched from py36 on centos8 to py39 on
centos9, these two tests started failing. Looks like a disagreement
about whether the canonical path for a bucket request should have
a trailing slash or not.
Mark them as known-failures for now so we can stay aware of any
other new breakage brought on by swift code changes.
Related-Change: I4f6b9c07af7bc768654f1a5d0c66b048e0f2c9c1
Change-Id: If990752c7ef7667182dbe18e49679e48c0e3d42d

This commit is contained in:

Tim Burke

2024年06月17日 15:58:56 -07:00

parent 46e183df15

commit 5be20f46df

1 changed files with 2 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
doc/s3api/conf/ceph-known-failures-tempauth.yaml

View File

@@ -58,6 +58,8 @@ ceph_s3:

s3tests_boto3.functional.test_headers.test_object_create_bad_contentlength_mismatch_below_aws2:{status:KNOWN}

s3tests_boto3.functional.test_headers.test_object_create_bad_contentlength_none:{status:KNOWN}

s3tests_boto3.functional.test_headers.test_object_create_bad_date_none_aws2:{status:KNOWN}

s3tests_boto3.functional.test_headers.test_bucket_create_bad_ua_empty_aws2:{status:KNOWN}

s3tests_boto3.functional.test_headers.test_bucket_create_bad_ua_none_aws2:{status:KNOWN}

s3tests_boto3.functional.test_s3.test_100_continue:{status:KNOWN}

s3tests_boto3.functional.test_s3.test_atomic_conditional_write_1mb:{status:KNOWN}

s3tests_boto3.functional.test_s3.test_atomic_dual_conditional_write_1mb:{status:KNOWN}

CI: update known failures for the ceph tests

2 doc/s3api/conf/ceph-known-failures-tempauth.yaml Unescape Escape View File

2
doc/s3api/conf/ceph-known-failures-tempauth.yaml

View File