ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jun aoki (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-7180) ambari build failure caused by ApacheDSContainer's working directory conflict.
Date Fri, 05 Sep 2014 22:27:28 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

jun aoki updated AMBARI-7180:
-----------------------------
    Description: 
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}

  was:
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.



> 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)

Mime
View raw message