[ 
https://issues.apache.org/jira/browse/HADOOP-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978917#comment-16978917
 ] 

Hudson commented on HADOOP-16687:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17680 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17680/])
HADOOP-16687. ABFS: Fix testcase added for HADOOP-16138 for namespace 
(iwasakims: rev de38045021875eac0558f06117942f5b849b4975)
* (edit) 
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azurebfs/ITestAzureBlobFileSystemCLI.java


> ABFS: Fix testcase added for HADOOP-16138 for namespace enabled account
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-16687
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16687
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>            Reporter: Sneha Vijayarajan
>            Assignee: Sneha Vijayarajan
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Test added as part of HADOOP-16138 : testMkdirRootNonExistentContainer() 
> fails at setup when run with a namespace enabled account (as GetAclStatus 
> call gets called in setup. For a non-namespace account, GetAclStatus being an 
> invalid operation will return 400 Bad request which is handled in base test 
> class.)
>  
> {noformat}
> Operation failed: "The specified filesystem does not exist.", 404, HEAD, 
> https://snvijayacontracttest.dfs.core.windows.net/abfs-testcontainer-998ff709-31b7-4d9e-bbaa-ae4c026d8500//?upn=false&action=getAccessControl&timeout=90Operation
>  failed: "The specified filesystem does not exist.", 404, HEAD, 
> https://snvijayacontracttest.dfs.core.windows.net/abfs-testcontainer-998ff709-31b7-4d9e-bbaa-ae4c026d8500//?upn=false&action=getAccessControl&timeout=90
> at 
> org.apache.hadoop.fs.azurebfs.services.AbfsRestOperation.execute(AbfsRestOperation.java:138)
>  at 
> org.apache.hadoop.fs.azurebfs.services.AbfsClient.getAclStatus(AbfsClient.java:516)
>  at 
> org.apache.hadoop.fs.azurebfs.services.AbfsClient.getAclStatus(AbfsClient.java:499)
>  at 
> org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.getIsNamespaceEnabled(AzureBlobFileSystemStore.java:216)
>  at 
> org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.getIsNamespaceEnabled(AzureBlobFileSystem.java:1108)
>  at 
> org.apache.hadoop.fs.azurebfs.AbstractAbfsIntegrationTest.setup(AbstractAbfsIntegrationTest.java:137)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498) at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>  at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>  at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>  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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
>  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
> java.lang.Thread.run(Thread.java:748){noformat}
> Even when run over with a non namespace enabled account, the test teardown 
> has failures, though not reported as a test failure. 
> {noformat}
> Operation failed: "The specified filesystem does not exist.", 404, DELETE, 
> https://snvijayaabfsnons.dfs.core.windows.net/abfs-testcontainer-bf33194a-6fcb-46b9-a0fa-7f458e9a6564?resource=filesystem&timeout=90,
>  FilesystemNotFound, "The specified filesystem does not exist. 
> RequestId:48c592a5-901f-0049-4671-940f4b000000 
> Time:2019-11-06T07:09:44.5098782Z"Operation failed: "The specified filesystem 
> does not exist.", 404, DELETE, 
> https://snvijayaabfsnons.dfs.core.windows.net/abfs-testcontainer-bf33194a-6fcb-46b9-a0fa-7f458e9a6564?resource=filesystem&timeout=90,
>  FilesystemNotFound, "The specified filesystem does not exist. 
> RequestId:48c592a5-901f-0049-4671-940f4b000000 
> Time:2019-11-06T07:09:44.5098782Z" 
> at 
> org.apache.hadoop.fs.azurebfs.services.AbfsRestOperation.execute(AbfsRestOperation.java:138)
>  at 
> org.apache.hadoop.fs.azurebfs.services.AbfsClient.deleteFilesystem(AbfsClient.java:225)
>  at 
> org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.deleteFilesystem(AzureBlobFileSystemStore.java:342)
>  at 
> org.apache.hadoop.fs.azurebfs.AbstractAbfsIntegrationTest.teardown(AbstractAbfsIntegrationTest.java:171)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498) at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>  at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>  at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>  at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) 
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
>  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
> java.lang.Thread.run(Thread.java:748){noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to