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

Martin Bukatovic commented on BIGTOP-1307:
------------------------------------------

I find out that it's not a bug in iTest shell object because you can configure 
sudo to allow passing PATH just for bigtop user, so it's rather a configuration 
issue, see BIGTOP-1326 for details. 

That said, the patch attached to this jira is still valid. Since the TestCLI 
needs to be run under hdfs user from start to end, it doesn't make sense to 
explicitly switch to hdfs (moreover this would need additional sudo 
configuration to allow hdfs user to switch to hdfs user :).

> Some TestCLI cases fail with 'No such file or directory'
> --------------------------------------------------------
>
>                 Key: BIGTOP-1307
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1307
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.8.0
>         Environment: HDP 2.0.6
>            Reporter: Martin Bukatovic
>            Assignee: Martin Bukatovic
>            Priority: Critical
>              Labels: test
>         Attachments: 
> 0001-BIGTOP-1307.-Do-not-switch-user-for-shell-object.patch, filter-cases.sh, 
> testcli.nosuchfile-cases.log
>
>
> I observe weird results of xml-defined test cases of TestCLI bigtop test:
> 136 test cases failed because of 'No such file or directory' error.
> To show what the problem is, see testcase #1:
> {noformat}
> 14/05/15 16:50:40 INFO cli.CLITestHelper: 
> -------------------------------------------
> 14/05/15 16:50:40 INFO cli.CLITestHelper:                     Test ID: [1]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:            Test Description: [ls: 
> file using absolute path]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:
> 14/05/15 16:50:40 INFO cli.CLITestHelper:               Test Commands: [-fs 
> hdfs://dhcp-lab-203.local:8020 -touchz /tmp/testcli_1400165386646/file1]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:               Test Commands: [-fs 
> hdfs://dhcp-lab-203.local:8020 -ls /tmp/testcli_1400165386646/file1]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:
> 14/05/15 16:50:40 INFO cli.CLITestHelper:            Cleanup Commands: [-fs 
> hdfs://dhcp-lab-203.local:8020 -rm /tmp/testcli_1400165386646/file1]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:
> 14/05/15 16:50:40 INFO cli.CLITestHelper:                  Comparator: 
> [TokenComparator]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:          Comparision result:   
> [fail]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:             Expected output:   
> [Found 1 items]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:               Actual output:   [ls: 
> `/tmp/testcli_1400165386646/file1': No such file or directory
> ]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:                  Comparator: 
> [RegexpComparator]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:          Comparision result:   
> [fail]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:             Expected output:   
> [^-rw-r--r--( )*1( )*[a-z]*( )*hdfs( )*0( )*[0-9]{4,}-[0-9]{2,}-[0-9]{2,} 
> [0-9]{2,}:[0-9]{2,}( )*/tmp/testcli_1400165386646/file1]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:               Actual output:   [ls: 
> `/tmp/testcli_1400165386646/file1': No such file or directory
> ]
> 14/05/15 16:50:40 INFO cli.CLITestHelper:
> 14/05/15 16:50:40 INFO cli.CLITestHelper: 
> -------------------------------------------
> {noformat}
> The results looks as if there were someting wrong with hadoop/hdfs.
> Nevertheless when I checked this particular case manually, it worked just 
> fine:
> {noformat}
> [bigtop@dhcp-lab-203 testcli]$ hadoop fs -mkdir /tmp/testcli_1400165386646
> [bigtop@dhcp-lab-203 testcli]$ hadoop fs -fs hdfs://dhcp-lab-203.local:8020 
> -touchz /tmp/testcli_1400165386646/file1
> [bigtop@dhcp-lab-203 testcli]$ hadoop fs -fs hdfs://dhcp-lab-203.local:8020 
> -ls /tmp/testcli_1400165386646/file1
> Found 1 items
> -rw-r--r--   3 bigtop hdfs          0 2014-05-15 17:08 
> /tmp/testcli_1400165386646/file1
> [bigtop@dhcp-lab-203 testcli]$ hadoop fs -fs hdfs://dhcp-lab-203.local:8020 
> -rm /tmp/testcli_1400165386646/file1
> 14/05/15 17:08:27 INFO fs.TrashPolicyDefault: Namenode trash configuration: 
> Deletion interval = 21600000 minutes, Emptier interval = 0 minutes.
> Moved: 'hdfs://dhcp-lab-203.local:8020/tmp/testcli_1400165386646/file1' to 
> trash at: hdfs://dhcp-lab-203.local:8020/user/bigtop/.Trash/Current
> [bigtop@dhcp-lab-203 testcli]$
> {noformat}
> I manually checked 5 other cases with the same result: when the testcase is 
> done
> manually, it works without any problems.
> Moreover I rerun all TestCLI cases 5 times, and the set of failed cases
> was always the same.
> Have anybody seen similar behaviour? I have executed TestCLI cases via wrapper
> which sets system classpath instead of maven defined enviromnent. Can this
> caused the issue, or is it likely that the problem is the bigtop tests? Also
> feel free to propose a way to debug this further.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to