ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13906) Cluster cannot be deleted when it is deployed via blueprint
Date Tue, 17 Nov 2015 04:16:11 GMT

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

Hudson commented on AMBARI-13906:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3847 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3847/])
AMBARI-13906. Cluster cannot be deleted when it is deployed via (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=55d0b18448542868d4f94abd388a46025d87ffbd])
* ambari-server/src/main/java/org/apache/ambari/server/orm/dao/TopologyRequestDAO.java
* ambari-server/src/test/java/org/apache/ambari/server/orm/dao/TopologyRequestDAOTest.java
* ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java


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

Mime
View raw message