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

jun aoki commented on AMBARI-7180:
----------------------------------

We are experience build failures 
https://builds.apache.org/job/Ambari-trunk-Commit/206/#showFailuresLink
The jira already exists https://issues.apache.org/jira/browse/AMBARI-7180 and 
I'm looking into it.

> ambari build failure caused by ApacheDSContainer's working directory conflict.
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-7180
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7180
>             Project: Ambari
>          Issue Type: Test
>            Reporter: jun aoki
>            Assignee: jun aoki
>
> Ambari jenkins build has been failing due to failures from 2 tests
> AmbariLdapAuthenticationProviderForDNWithSpaceTest 
> and 
> AmbariLdapAuthenticationProviderTest
> https://builds.apache.org/job/Ambari-trunk-Commit/158/testReport/
> They are caused due to a working directory conflict. The tests use 
> ApacheDSContainer and it creates a hard code working directory 
> (/tmp/apacheds-spring-security), and it seems for some reasons, it was not 
> deleted property from previous execution.
> {code}
> java.lang.IllegalArgumentException: The specified working directory 
> '/tmp/apacheds-spring-security' already exists. Another directory service 
> instance may be using it or it may be from a  previous unclean shutdown. 
> Please confirm and delete it or configure a different working directory
>       at 
> org.springframework.security.ldap.server.ApacheDSContainer.setWorkingDirectory(ApacheDSContainer.java:132)
>       at 
> org.springframework.security.ldap.server.ApacheDSContainer.afterPropertiesSet(ApacheDSContainer.java:109)
>       at 
> org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderTest.beforeClass(AmbariLdapAuthenticationProviderTest.java:62)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to