-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-16477. S3 delegation token tests fail if fs.s3a.encryption.key set #1210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Testing: S3 Ireland with s3guard and KMS. Currently failing |
Update. Yes, the IAM role I was assuming didn't have the right permissions. Plan
|
Assumed role/DT tests all happy once IAM role is fixed up SSE-C tests failing, with cause (As seen by debugger) that the kms key option isn't being unset. If the options were being set in a jceks file I'd understand this (you can't unset those & they take priority over Config map changes), but that's not it .Needs more debug time |
HADOOP-16626 should help set things up reliably here. |
4224b06
to
a8cb78b
Compare
🎊 +1 overall
This message was automatically generated. |
This PR also handles the case where the config explicitly sets the DT binding for the store, which needs to be unset for all tests playing with AWS auth chains |
Not sure if this is ready for review or not. I'm +1 if the tests are passing. |
thanks for the vote Sid, will review the docs and retest |
… set * Delegation Token In FileSystem tests unset more options and compare propagation of entries * Added a spurious ITestRoleDelegationInFilesystem override so I can debug things better. SSEC tests fail too...need to understand that Change-Id: Icbd418f9aa6c72312d39b4d94a1f2a2854fca059
Change-Id: Iac491d15bcb088b93cea94401c6ec41076095b8d
Rebased to trunk with the changes of HADOOP-16626 stopping per-bucket options creeping back in. I believe that issue is why the patch failed to work before Change-Id: I4ab65cd99fe4c5e8b5594f436e50483bd63e7983
* all IAM roles need to include KMS R/W access * unset encryption for the checksum test * remove DT Binding when it interferes with tests of AWS credential providers. Change-Id: I2e532f3a272e76bb3f97af313d4454e28ce69e97
…MSE problem. Also changed `operation` on writes from `put` to `Writing Object` as that is what is actually happening. Change-Id: Ib3491984faaf9c15c6711a6c65b9c2eca28ddeb6
9cf6f07
to
aca67f5
Compare
|
||
``` | ||
java.nio.file.AccessDeniedException: test/testDTFileSystemClient: Writing Object on test/testDTFileSystemClient: | ||
com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whitespace:end of line
💔 -1 overall
This message was automatically generated. |
It looks like the AWS Permissions Policy created for the Role DT (and passed into AssumeRole) isn't asking for the right KMS permissions for a PUT request to work. At least, it's mkdirs that fails first...we should verify read of existing data too). I don't currently understand what is wrong with the permissions I am asking for.
Or maybe it's actually the role which is blocked? That would explain things -the code is valid, but the role is too restricted. Needs more investigation, and no doubt some more entries in the troubleshooting docs
Change-Id: Icbd418f9aa6c72312d39b4d94a1f2a2854fca059