[
https://issues.apache.org/jira/browse/HADOOP-13125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278598#comment-15278598
]
Steve Loughran commented on HADOOP-13125:
-----------------------------------------
after
{code}
testReadNullBuffer(org.apache.hadoop.fs.contract.s3a.TestS3AContractSeek) Time
elapsed: 0.043 sec <<< ERROR!
java.io.IOException: Unable to initialize filesystem s3a://tests3neu/:
java.lang.IllegalArgumentException: unknown signer type: AES256
at
org.apache.hadoop.fs.contract.AbstractBondedFSContract.init(AbstractBondedFSContract.java:76)
at
org.apache.hadoop.fs.contract.AbstractFSContractTestBase.setup(AbstractFSContractTestBase.java:165)
at
org.apache.hadoop.fs.contract.AbstractContractSeekTest.setup(AbstractContractSeekTest.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
Caused by: java.lang.IllegalArgumentException: unknown signer type: AES256
at com.amazonaws.auth.SignerFactory.createSigner(SignerFactory.java:118)
at
com.amazonaws.auth.SignerFactory.getSignerByTypeAndService(SignerFactory.java:95)
at
com.amazonaws.AmazonWebServiceClient.computeSignerByServiceRegion(AmazonWebServiceClient.java:321)
at
com.amazonaws.AmazonWebServiceClient.computeSignerByURI(AmazonWebServiceClient.java:294)
at
com.amazonaws.AmazonWebServiceClient.setEndpoint(AmazonWebServiceClient.java:170)
at
com.amazonaws.services.s3.AmazonS3Client.setEndpoint(AmazonS3Client.java:519)
at
com.amazonaws.services.s3.AmazonS3Client.init(AmazonS3Client.java:492)
at
com.amazonaws.services.s3.AmazonS3Client.<init>(AmazonS3Client.java:436)
at
com.amazonaws.services.s3.AmazonS3Client.<init>(AmazonS3Client.java:416)
at
org.apache.hadoop.fs.s3a.S3AFileSystem.initAmazonS3Client(S3AFileSystem.java:325)
at
org.apache.hadoop.fs.s3a.S3AFileSystem.initialize(S3AFileSystem.java:221)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2785)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2822)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2804)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:381)
at
org.apache.hadoop.fs.contract.AbstractBondedFSContract.init(AbstractBondedFSContract.java:72)
at
org.apache.hadoop.fs.contract.AbstractFSContractTestBase.setup(AbstractFSContractTestBase.java:165)
at
org.apache.hadoop.fs.contract.AbstractContractSeekTest.setup(AbstractContractSeekTest.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
{code}
> FS Contract tests don't report FS initialization errors well
> ------------------------------------------------------------
>
> Key: HADOOP-13125
> URL: https://issues.apache.org/jira/browse/HADOOP-13125
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> If the {{FileSystem.initialize()}} method of an FS fails with an
> IllegalArgumentException, the FS contract tests assume this is related to the
> URI syntax and raises a new exception 'invalid URI'+ fsURI, retaining the
> real cause only as error text in the nested exception.
> the exception text should be included in the message thrown, and cause
> changed to indicate that it's initialization related.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
