[
https://issues.apache.org/jira/browse/HADOOP-19512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938187#comment-17938187
]
Steve Loughran commented on HADOOP-19512:
-----------------------------------------
All my role tests are failing against an s3 express bucket. There is probably
some permission I have to add either in my restricted role or in the role
restrictions applied.
{code}
[ERROR] ITestPartialRenamesDeletes.testCopyDirFailsToReadOnlyDir
[ERROR] Run 1:
s3a://stevel--usw2-az1--x-s3/job-00-fork-0004/test/testCopyDirFailsToReadOnlyDir[bulk-delete=false]-single-1742899868.713/writableDir:
getFileStatus on
s3a://stevel--usw2-az1--x-s3/job-00-fork-0004/test/testCopyDirFailsToReadOnlyDir[bulk-delete=false]-single-1742899868.713/writableDir:
software.amazon.awssdk.services.s3.model.S3Exception: Access Denied (Service:
S3, Status Code: 403, Request ID: 0177452246000195cced7c8e0509ce6cff116d40,
Extended Request ID: tm9SdOAoacKcz3):AccessDenied
[ERROR] Run 2:
s3a://stevel--usw2-az1--x-s3/job-00-fork-0004/test/testCopyDirFailsToReadOnlyDir[bulk-delete=true]-multi-1742899942.248/writableDir:
getFileStatus on
s3a://stevel--usw2-az1--x-s3/job-00-fork-0004/test/testCopyDirFailsToReadOnlyDir[bulk-delete=true]-multi-1742899942.248/writableDir:
software.amazon.awssdk.services.s3.model.S3Exception: Access Denied (Service:
S3, Status Code: 403, Request ID: 0156a03462000195ccee9bc40509e3559b0dc62f,
Extended Request ID: 4XGsZa):AccessDenied
{code}
> S3A: Test failures testing with unusual bucket configurations
> -------------------------------------------------------------
>
> Key: HADOOP-19512
> URL: https://issues.apache.org/jira/browse/HADOOP-19512
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.5.0, 3.4.2
> Reporter: Steve Loughran
> Assignee: Ahmar Suhail
> Priority: Minor
> Attachments: test-failures.txt
>
>
> 1. The logic to skip vector IO contract tests doesn't work if the analytics
> stream is set on a per-bucket basis for the test bucket
> 2. tests with SSE-C are failing. Test bucket is normally set up to use
> SSE-KMS, FWIW
> {code}
> <property>
> <name>fs.s3a.bucket.stevel-london.encryption.algorithm</name>
> <value>SSE-KMS</value>
> </property>
> {code}
> this only happens when the analytics stream is set for the test bucket
> fs.s3a.bucket.stevel-london.input.stream.type=analytics; set it globally all
> is good
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
