ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-14674) Cannot Finalize Downgrade Due To Detached ClusterEntity
Date Fri, 15 Jan 2016 07:11:39 GMT


Hadoop QA commented on AMBARI-14674:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:
Console output:

This message is automatically generated.

> Cannot Finalize Downgrade Due To Detached ClusterEntity
> -------------------------------------------------------
>                 Key: AMBARI-14674
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.1
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.2.1
>         Attachments: AMBARI-14674.patch
> RU HDP 2.2 to 2.4 downgrade results in:
> {code}
> java.lang.IllegalArgumentException: Can not refresh not managed object: org.apache.ambari.server.orm.entities.ClusterEntity@18126.
> 	at org.eclipse.persistence.internal.jpa.EntityManagerImpl.refresh(
> 	at org.eclipse.persistence.internal.jpa.EntityManagerImpl.refresh(
> 	at org.apache.ambari.server.orm.dao.ClusterDAO.refresh(
> 	at org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(
> 	at org.apache.ambari.server.state.cluster.ClusterImpl.removeConfigurations(
> 	at org.apache.ambari.server.serveraction.upgrades.FinalizeUpgradeAction.finalizeDowngrade(
> 	at org.apache.ambari.server.serveraction.upgrades.FinalizeUpgradeAction.execute(
> 	at org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(
> 	at org.apache.ambari.server.serveraction.ServerActionExecutor$
> 	at
> {code}
> It seems like what's happening is that the ClusterEntity is being retrieved outside of
a JPA session. Although the ClusterDAO creates the session, it also ends it, leaving the Entity
detached. We should instead be refreshing this Entity within the bounds of the Transaction.

This message was sent by Atlassian JIRA

View raw message