ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9934) Deregister Stack Version error if it has been already INSTALLED or INSTALL_FAILED on some cluster
Date Thu, 19 Mar 2015 16:22:39 GMT

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

Dmitry Lysnichenko commented on AMBARI-9934:
--------------------------------------------

[~jluniya],
yes, this is still an issue. It's non-critical, but requires complicated JPA changes (at least
complicated enough to be moved out of 2.0.0). The issue has been decided to be moved to 2.1.0

> Deregister Stack Version error if it has been already INSTALLED or INSTALL_FAILED on
some cluster
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9934
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9934
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0
>
>
> 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)

Mime
View raw message