ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15348) Ambari upgrade/start commands should detect any ambari-server hotfix and fail upgrade/start from proceeding
Date Mon, 14 Mar 2016 14:24:33 GMT

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

Hudson commented on AMBARI-15348:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #506 (See [https://builds.apache.org/job/Ambari-branch-2.2/506/])
AMBARI-15348 Ambari upgrade/start commands should detect any (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1760ef283c1323e4eb237d70fc17faa39c54df08])
* ambari-server/src/main/package/rpm/preinstall.sh
* ambari-server/src/main/package/deb/control/preinst
* ambari-server/pom.xml
* ambari-server/src/test/python/TestServerClassPath.py
* ambari-server/src/main/python/ambari_server/serverClassPath.py


> Ambari upgrade/start commands should detect any ambari-server hotfix and fail upgrade/start
from proceeding
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15348
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15348
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15348-trunk.patch
>
>
> If user copied hotfixed ambari-server.jar to /usr/lib/ambari-server and didn't remove
the hotfix, the upgrade will fails with error:
> {code}
> Internal Exception: Exception [EclipseLink-7250] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
org.eclipse.persistence.exceptions.ValidationException
> Exception Description: [class org.apache.ambari.server.orm.entities.HostEntity] uses
a non-entity [class org.apache.ambari.server.orm.entities.HostVersionEntity] as target entity
in the relationship attribute [field hostVersionEntities].
>         at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.createPredeployFailedPersistenceException(EntityManagerSetupImpl.java:1954)
>         at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1945)
>         at org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.callPredeploy(JPAInitializer.java:98)
>         at org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactoryImpl(PersistenceProvider.java:96)
>         ... 15 more
> Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
org.eclipse.persistence.exceptions.EntityManagerSetupException
> Exception Description: Predeployment of PersistenceUnit [ambari-server] failed.
> {code}
> As a workaround, user needs to restore all the database and configuration, remove all
the hotfix and run "ambari-server upgrade" again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message