ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19347) Previous Upgrade In Progress Pre-Req Check Incorrectly Detects ABORTED Upgrade
Date Tue, 03 Jan 2017 22:14:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hurley updated AMBARI-19347:
-------------------------------------
    Attachment: AMBARI-19347.patch

> 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)

Mime
View raw message