You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Sebastian Toader <st...@hortonworks.com> on 2015/11/16 18:44:40 UTC

Review Request 40354: Cluster cannot be deleted when it is deployed via blueprint

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40354/
-----------------------------------------------------------

Review request for Ambari, Alejandro Fernandez, Sumit Mohanty, and Sid Wagle.


Bugs: AMBARI-13906
    https://issues.apache.org/jira/browse/AMBARI-13906


Repository: ambari


Description
-------

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)


Diffs
-----

  ambari-server/src/main/java/org/apache/ambari/server/orm/dao/TopologyRequestDAO.java 65cd59f 
  ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java a3979c1 
  ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java 24c7bce 
  ambari-server/src/test/java/org/apache/ambari/server/orm/dao/TopologyRequestDAOTest.java f5ece39 
  ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java 2d9d779 

Diff: https://reviews.apache.org/r/40354/diff/


Testing
-------

1. Manual testing:
- Deployed a 3 node cluster using Blueprint. Stopped all services than deleted the cluster using the Ambari Rest API.
- Deployed a 3 node cluster using the wizzard. Stopped all services than deleted the cluster using the Ambari Rest API.


2. Ambari-server unit tests
----------------------------------------------------------------------
Ran 249 tests in 6.523s

OK
----------------------------------------------------------------------
Total run:794
Total errors:0
Total failures:0
OK


Thanks,

Sebastian Toader

Re: Review Request 40354: Cluster cannot be deleted when it is deployed via blueprint

Posted by Alejandro Fernandez <af...@hortonworks.com>.

> On Nov. 16, 2015, 7:25 p.m., Alejandro Fernandez wrote:
> > Ship It!

Pushed to trunk,
commit 55d0b18448542868d4f94abd388a46025d87ffbd

Pushed to branch-2.1,
commit ea0a4bed7d9a26b9d5bd0a1d28a1dbf1374be2f0


- Alejandro


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40354/#review106706
-----------------------------------------------------------


On Nov. 16, 2015, 5:44 p.m., Sebastian Toader wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40354/
> -----------------------------------------------------------
> 
> (Updated Nov. 16, 2015, 5:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13906
>     https://issues.apache.org/jira/browse/AMBARI-13906
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> 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)
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/TopologyRequestDAO.java 65cd59f 
>   ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java a3979c1 
>   ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java 24c7bce 
>   ambari-server/src/test/java/org/apache/ambari/server/orm/dao/TopologyRequestDAOTest.java f5ece39 
>   ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java 2d9d779 
> 
> Diff: https://reviews.apache.org/r/40354/diff/
> 
> 
> Testing
> -------
> 
> 1. Manual testing:
> - Deployed a 3 node cluster using Blueprint. Stopped all services than deleted the cluster using the Ambari Rest API.
> - Deployed a 3 node cluster using the wizzard. Stopped all services than deleted the cluster using the Ambari Rest API.
> 
> 
> 2. Ambari-server unit tests
> ----------------------------------------------------------------------
> Ran 249 tests in 6.523s
> 
> OK
> ----------------------------------------------------------------------
> Total run:794
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

Re: Review Request 40354: Cluster cannot be deleted when it is deployed via blueprint

Posted by Alejandro Fernandez <af...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40354/#review106706
-----------------------------------------------------------

Ship it!


Ship It!

- Alejandro Fernandez


On Nov. 16, 2015, 5:44 p.m., Sebastian Toader wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40354/
> -----------------------------------------------------------
> 
> (Updated Nov. 16, 2015, 5:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13906
>     https://issues.apache.org/jira/browse/AMBARI-13906
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> 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)
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/TopologyRequestDAO.java 65cd59f 
>   ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java a3979c1 
>   ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java 24c7bce 
>   ambari-server/src/test/java/org/apache/ambari/server/orm/dao/TopologyRequestDAOTest.java f5ece39 
>   ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java 2d9d779 
> 
> Diff: https://reviews.apache.org/r/40354/diff/
> 
> 
> Testing
> -------
> 
> 1. Manual testing:
> - Deployed a 3 node cluster using Blueprint. Stopped all services than deleted the cluster using the Ambari Rest API.
> - Deployed a 3 node cluster using the wizzard. Stopped all services than deleted the cluster using the Ambari Rest API.
> 
> 
> 2. Ambari-server unit tests
> ----------------------------------------------------------------------
> Ran 249 tests in 6.523s
> 
> OK
> ----------------------------------------------------------------------
> Total run:794
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

Re: Review Request 40354: Cluster cannot be deleted when it is deployed via blueprint

Posted by Sumit Mohanty <sm...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40354/#review106690
-----------------------------------------------------------

Ship it!


Ship It!

- Sumit Mohanty


On Nov. 16, 2015, 5:44 p.m., Sebastian Toader wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40354/
> -----------------------------------------------------------
> 
> (Updated Nov. 16, 2015, 5:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13906
>     https://issues.apache.org/jira/browse/AMBARI-13906
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> 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)
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/TopologyRequestDAO.java 65cd59f 
>   ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java a3979c1 
>   ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java 24c7bce 
>   ambari-server/src/test/java/org/apache/ambari/server/orm/dao/TopologyRequestDAOTest.java f5ece39 
>   ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java 2d9d779 
> 
> Diff: https://reviews.apache.org/r/40354/diff/
> 
> 
> Testing
> -------
> 
> 1. Manual testing:
> - Deployed a 3 node cluster using Blueprint. Stopped all services than deleted the cluster using the Ambari Rest API.
> - Deployed a 3 node cluster using the wizzard. Stopped all services than deleted the cluster using the Ambari Rest API.
> 
> 
> 2. Ambari-server unit tests
> ----------------------------------------------------------------------
> Ran 249 tests in 6.523s
> 
> OK
> ----------------------------------------------------------------------
> Total run:794
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

Re: Review Request 40354: Cluster cannot be deleted when it is deployed via blueprint

Posted by Sid Wagle <sw...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40354/#review106769
-----------------------------------------------------------

Ship it!


Ship It!

- Sid Wagle


On Nov. 16, 2015, 5:44 p.m., Sebastian Toader wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40354/
> -----------------------------------------------------------
> 
> (Updated Nov. 16, 2015, 5:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13906
>     https://issues.apache.org/jira/browse/AMBARI-13906
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> 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)
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/TopologyRequestDAO.java 65cd59f 
>   ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java a3979c1 
>   ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java 24c7bce 
>   ambari-server/src/test/java/org/apache/ambari/server/orm/dao/TopologyRequestDAOTest.java f5ece39 
>   ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java 2d9d779 
> 
> Diff: https://reviews.apache.org/r/40354/diff/
> 
> 
> Testing
> -------
> 
> 1. Manual testing:
> - Deployed a 3 node cluster using Blueprint. Stopped all services than deleted the cluster using the Ambari Rest API.
> - Deployed a 3 node cluster using the wizzard. Stopped all services than deleted the cluster using the Ambari Rest API.
> 
> 
> 2. Ambari-server unit tests
> ----------------------------------------------------------------------
> Ran 249 tests in 6.523s
> 
> OK
> ----------------------------------------------------------------------
> Total run:794
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>