[
https://issues.apache.org/jira/browse/HADOOP-19336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898697#comment-17898697
]
ASF GitHub Bot commented on HADOOP-19336:
-----------------------------------------
shameersss1 opened a new pull request, #7164:
URL: https://github.com/apache/hadoop/pull/7164
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Test fix and documentation changes. This commit does the following
1. Moved troubleshooting steps of encryption from troubleshooting into
encryption.md
2. Skipped tests when CSE is enabled for
```
ITestAwsSdkWorkarounds.testNoisyLogging
ITestUploadRecovery.testCommitOperations
ITestUploadRecovery.testMagicWriteRecovery
```
The reason for the same is mentioned
[here](https://issues.apache.org/jira/browse/HADOOP-19336?focusedCommentId=17898633&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17898633)
### How was this patch tested?
tested in us-east-1 with (both per bucket and base s3 configuration )
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ x] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> S3A: Test failures after CSE support added
> ------------------------------------------
>
> Key: HADOOP-19336
> URL: https://issues.apache.org/jira/browse/HADOOP-19336
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.5.0
> Reporter: Steve Loughran
> Assignee: Syed Shameerur Rahman
> Priority: Major
>
> Testing hadoop trunk with CSE-KMS configured I get
> * 400 error without region set (KMS providing nothing helpful). Proposed:
> move troubleshooting into encryption.md, cover 400 and this as a possible cuse
> * test failures
> {code}
> [ERROR]
> ITestS3AClientSideEncryptionKms>ITestS3AClientSideEncryption.testSizeOfEncryptedObjectFromHeaderWithV1Compatibility:345->ITestS3AClientSideEncryption.assertFileLength:447
> [Length of
> s3a://stevel-london/job-00-fork-0009/test/testSizeOfEncryptedObjectFromHeaderWithV1Compatibility/file
> status:
> S3AFileStatus{path=s3a://stevel-london/job-00-fork-0009/test/testSizeOfEncryptedObjectFromHeaderWithV1Compatibility/file;
> isDirectory=false; length=1024; replication=1; blocksize=33554432;
> modification_time=1731674289000; access_time=0; owner=stevel; group=stevel;
> permission=rw-rw-rw-; isSymlink=false; hasAcl=false; isEncrypted=true;
> isErasureCoded=false} isEmptyDirectory=FALSE
> eTag="0f343b0931126a20f133d67c2b018a3b"
> versionId=JyA1I_OW8osQTS3zWdn_Z0qlQYqBZ_7.] expected:<10[]L> but was:<10[24]L>
> [ERROR] ITestAwsSdkWorkarounds.testNoisyLogging:99 [LOG output does not
> contain the forbidden text. Has the SDK been fixed?]
> Expecting:
> <"">
> to contain:
> <"The provided S3AsyncClient is an instance of MultipartS3AsyncClient">
> [ERROR] Errors:
> [ERROR] ITestUploadRecovery.testCommitOperations:234 » AWSClientIO upload
> part #1 uplo...
> [ERROR] ITestUploadRecovery.testMagicWriteRecovery[array-commit-true] »
> AWSClientIO up...
> [ERROR] ITestUploadRecovery.testMagicWriteRecovery[bytebuffer-commit-false]
> » AWSClientIO
> [ERROR] ITestUploadRecovery.testMagicWriteRecovery[disk-commit-false] »
> AWSClientIO up...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
