[
https://issues.apache.org/jira/browse/AMBARI-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101343#comment-15101343
]
Hadoop QA commented on AMBARI-14674:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12782362/AMBARI-14674.patch
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 tests.
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:
https://builds.apache.org/job/Ambari-trunk-test-patch/4925//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4925//console
This message is automatically generated.
> Cannot Finalize Downgrade Due To Detached ClusterEntity
> -------------------------------------------------------
>
> Key: AMBARI-14674
> URL: https://issues.apache.org/jira/browse/AMBARI-14674
> 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(EntityManagerImpl.java:1024)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.refresh(EntityManagerImpl.java:929)
> at
> org.apache.ambari.server.orm.dao.ClusterDAO.refresh(ClusterDAO.java:309)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:68)
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.removeConfigurations(ClusterImpl.java:3216)
> at
> org.apache.ambari.server.serveraction.upgrades.FinalizeUpgradeAction.finalizeDowngrade(FinalizeUpgradeAction.java:314)
> at
> org.apache.ambari.server.serveraction.upgrades.FinalizeUpgradeAction.execute(FinalizeUpgradeAction.java:116)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:537)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:474)
> at java.lang.Thread.run(Thread.java:745)
> {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
(v6.3.4#6332)
