ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (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 Wed, 09 Mar 2016 17:26:41 GMT

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

Hadoop QA commented on AMBARI-15348:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12792244/AMBARI-15348-trunk.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5783//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5783//console

This message is automatically generated.

> 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