Details
-
Test
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.2.0
Description
In Apache ozone.om.enable.filesystem.paths is set to false where we do not normalize paths, so the test expects the path to be not normalized in the list. So the test would fail when the setting is set to true:
Secure S3 put-object test | FAIL |
'{
"Contents": [
,
{ "LastModified": "2021-04-28T04:37:22.787Z", "ETag": "2021-04-28T04:37:22.787Z", "StorageClass": "STANDARD", "Key": "tmp1/tmp2/", "Size": 0 },
{ "LastModified": "2021-04-28T04:37:24.548Z", "ETag": "2021-04-28T04:37:24.548Z", "StorageClass": "STANDARD", [ Message content over the limit has been removed. ] "StorageClass": "STANDARD", "Key": "tmp3/", "Size": 0 },
{ "LastModified": "2021-04-28T04:37:26.001Z", "ETag": "2021-04-28T04:37:26.001Z", "StorageClass": "STANDARD", "Key": "tmp3/tmp4/", "Size": 0 },
{ "LastModified": "2021-04-28T04:37:26.103Z", "ETag": "2021-04-28T04:37:26.103Z", "StorageClass": "STANDARD", "Key": "tmp3/tmp4/NOTICE.txt", "Size": 17539 }]
}' does not contain 'tmp3//tmp4/NOTICE.txt'
------------------------------------------------------------------------------
Secure S3 test Failure | PASS |
------------------------------------------------------------------------------
Security.Ozone-Secure-S3 :: Smoke test to start cluster with docke... | FAIL |
3 tests, 2 passed, 1 failed
To fix this, we can check the setting ozone.om.enable.filesystem.paths and verify accordingly - whether or not expecting path normalization.
Attachments
Issue Links
- is superceded by
-
HDDS-7495 Create OBS buckets by default from S3 API
- Resolved