[
https://issues.apache.org/jira/browse/HADOOP-12851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172981#comment-15172981
]
Chris Nauroth commented on HADOOP-12851:
----------------------------------------
[~lmccay], in patch v03, in {{TestS3AConfiguration}}, is this line...
{code}
provisionAccessKeys(conf);
{code}
...supposed to use the modified configuration instead?
{code}
provisionAccessKeys(c);
{code}
Currently, I see the failure shown below, but the test passes if I make that
change.
{code}
Running org.apache.hadoop.fs.s3a.TestS3AConfiguration
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.594 sec <<<
FAILURE! - in org.apache.hadoop.fs.s3a.TestS3AConfiguration
testExcludingS3ACredentialProvider(org.apache.hadoop.fs.s3a.TestS3AConfiguration)
Time elapsed: 1.461 sec <<< ERROR!
java.lang.IllegalArgumentException: The bucketName parameter must be specified.
at
com.amazonaws.services.s3.AmazonS3Client.rejectNull(AmazonS3Client.java:3032)
at
com.amazonaws.services.s3.AmazonS3Client.headBucket(AmazonS3Client.java:1102)
at
com.amazonaws.services.s3.AmazonS3Client.doesBucketExist(AmazonS3Client.java:1070)
at
org.apache.hadoop.fs.s3a.S3AFileSystem.initialize(S3AFileSystem.java:177)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2790)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2827)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2809)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:381)
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:294)
at
org.apache.hadoop.security.alias.JavaKeyStoreProvider.initFileSystem(JavaKeyStoreProvider.java:89)
at
org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.<init>(AbstractJavaKeyStoreProvider.java:82)
at
org.apache.hadoop.security.alias.JavaKeyStoreProvider.<init>(JavaKeyStoreProvider.java:49)
at
org.apache.hadoop.security.alias.JavaKeyStoreProvider.<init>(JavaKeyStoreProvider.java:41)
at
org.apache.hadoop.security.alias.JavaKeyStoreProvider$Factory.createProvider(JavaKeyStoreProvider.java:100)
at
org.apache.hadoop.security.alias.CredentialProviderFactory.getProviders(CredentialProviderFactory.java:58)
at
org.apache.hadoop.fs.s3a.TestS3AConfiguration.provisionAccessKeys(TestS3AConfiguration.java:221)
at
org.apache.hadoop.fs.s3a.TestS3AConfiguration.testExcludingS3ACredentialProvider(TestS3AConfiguration.java:342)
{code}
> S3AFileSystem Uptake of ProviderUtils.excludeIncompatibleCredentialProviders
> ----------------------------------------------------------------------------
>
> Key: HADOOP-12851
> URL: https://issues.apache.org/jira/browse/HADOOP-12851
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Larry McCay
> Assignee: Larry McCay
> Attachments: HADOOP-12851-001.patch, HADOOP-12851-002.patch,
> HADOOP-12851-003.patch
>
>
> HADOOP-12846 introduced the ability for FileSystem based integration points
> of credential providers to eliminate the threat of a recursive infinite loop
> due to a provider in the same filesystem being configured.
> It was WASB has already uptaken its use in HADOOP-12846 and this patch will
> add it to the S3A integration point as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
