[
https://issues.apache.org/jira/browse/AMBARI-13906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007596#comment-15007596
]
Hadoop QA commented on AMBARI-13906:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12772534/AMBARI-13906.v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.security.authorization.AmbariLdapAuthenticationProviderForDNWithSpaceTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4295//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4295//console
This message is automatically generated.
> Cluster cannot be deleted when it is deployed via blueprint
> -----------------------------------------------------------
>
> Key: AMBARI-13906
> URL: https://issues.apache.org/jira/browse/AMBARI-13906
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Fix For: 2.1.3
>
> Attachments: AMBARI-13906.v1.patch
>
>
> 13 Nov 2015 01:04:23,938 ERROR [qtp-client-6549]
> AmbariJpaLocalTxnInterceptor:114 - [DETAILED ERROR] Rollback reason:
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: update or
> delete on table "clusters" violates foreign key constraint
> "fk_topology_request_cluster_id" on table "topology_request"
> Detail: Key (cluster_id)=(2) is still referenced from table
> "topology_request".
> Error Code: 0
> Call: DELETE FROM clusters WHERE (cluster_id = ?)
> bind => [1 parameter bound]
> Query:
> DeleteObjectQuery(org.apache.ambari.server.orm.entities.ResourceEntity@5ec69e94)
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1611)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:898)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:962)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:631)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:603)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
