Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 10 Nov 2016 12:03:59 +0000 (UTC)
From: "Andrii Tkach (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13019805.1478777597000.243751.1478779439857@Atlassian.JIRA>
In-Reply-To: <JIRA.13019805.1478777597000@Atlassian.JIRA>
References: <JIRA.13019805.1478777597000@Atlassian.JIRA> <JIRA.13019805.1478777597358@arcas>
Subject: [jira] [Updated] (AMBARI-18844) Web Client Should Support
 HOST_ORDERED Upgrades In Progress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 10 Nov 2016 12:04:01 -0000


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

Andrii Tkach updated AMBARI-18844:
----------------------------------
    Attachment: AMBARI-18844.patch

> Web Client Should Support HOST_ORDERED Upgrades In Progress
> -----------------------------------------------------------
>
>                 Key: AMBARI-18844
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18844
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18844.patch, AMBARI-18844_branch-2.5.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't show up as an upgrade "In Progress" in the web client. Although this upgrade type is not going to be exposed as a first-class upgrade type for Ambari 2.5, the web client must still behave correctly when encountering a {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove hosts/services, changing configs, etc, should be prevented.


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