ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-10874) Pre-Upgrade Checks Should Know Which Stack They Are Valid
Date Fri, 01 May 2015 13:36:06 GMT

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

Jonathan Hurley resolved AMBARI-10874.
--------------------------------------
    Resolution: Fixed

> Pre-Upgrade Checks Should Know Which Stack They Are Valid
> ---------------------------------------------------------
>
>                 Key: AMBARI-10874
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10874
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> With rolling upgrades now possible within a stack (HDP 2.2.x.x -> HDP 2.2.y.y) and
between stacks (HDP 2.2 -> HDP 2.3), the pre-upgrade checks are not longer valid for all
upgrade scenarios.
> Instead, each upgrade check should be aware of which stack upgrade they are valid for.
On upgrading, Ambari will produce a list of pre-upgrade checks that are valid for the specific
source and target stacks only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message