[
https://issues.apache.org/jira/browse/AMBARI-19347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799632#comment-15799632
]
Hudson commented on AMBARI-19347:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6355 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6355/])
AMBARI-19347 - Previous Upgrade In Progress Pre-Req Check Incorrectly (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f207b95f586a5d218d0059c767825d1baa6bd856])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/PreviousUpgradeCompleted.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UpgradeDAO.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/host-ordered-upgrade.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/PreviousUpgradeCompletedTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
> Previous Upgrade In Progress Pre-Req Check Incorrectly Detects ABORTED Upgrade
> ------------------------------------------------------------------------------
>
> Key: AMBARI-19347
> URL: https://issues.apache.org/jira/browse/AMBARI-19347
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19347.patch
>
>
> Due to the fix made for
> AMBARI-19053, the prereq check for previously created needs to be corrected
> for determining the downgrade that matched the failed upgrade.
> The original logic for this check was overly complex (and kind of wrong). It
> ignored the state of the downgrade if one existed. In reality, we should care
> about the "last" downgrade and what its state is. Additionally, checking for
> `FinalizeUpgradeAction` as part of the commands in an upgrade is problematic
> for upgrades which may not have this command on different stacks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
