You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2015/03/24 15:55:52 UTC
[jira] [Resolved] (AMBARI-10151) Deregister Stack Version error if
it has been already INSTALLED or INSTALL_FAILED on some cluster
[ https://issues.apache.org/jira/browse/AMBARI-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaly Brodetskyi resolved AMBARI-10151.
----------------------------------------
Resolution: Fixed
Committed to trunk
> Deregister Stack Version error if it has been already INSTALLED or INSTALL_FAILED on some cluster
> -------------------------------------------------------------------------------------------------
>
> Key: AMBARI-10151
> URL: https://issues.apache.org/jira/browse/AMBARI-10151
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-10151.patch
>
>
> Install HDP-2.2.1-2214 and register HDP-2.2.1-2275.
> Try installing bits (it failed)
> Try to deregister HDP-2.2.1-2275
> Error appears:
> {code}
> Version delete error
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.2.v20130514-5956486): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.BatchUpdateException: Batch entry 0 DELETE FROM repo_version WHERE (repo_version_id = 3) was aborted. Call getNextException to see the cause. Error Code: 0 Call: DELETE FROM repo_version WHERE (repo_version_id = ?) bind => [1 parameter bound]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)