Return-Path: 
 <dev-return-77005-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E7860178E1
	for <apmail-ambari-dev-archive@www.apache.org>;
 Tue, 16 Jun 2015 01:28:00 +0000 (UTC)
Received: (qmail 30342 invoked by uid 500); 16 Jun 2015 01:28:00 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 30307 invoked by uid 500); 16 Jun 2015 01:28:00 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 30295 invoked by uid 99); 16 Jun 2015 01:28:00 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2015 01:28:00 +0000
Date: Tue, 16 Jun 2015 01:28:00 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12838012.1434418024000.79204.1434418080661@Atlassian.JIRA>
In-Reply-To: <JIRA.12838012.1434418024000@Atlassian.JIRA>
References: <JIRA.12838012.1434418024000@Atlassian.JIRA>
 <JIRA.12838012.1434418024506@arcas>
Subject: [jira] [Created] (AMBARI-11939) Upgrades Placed Into ABORTED Status
 Show As COMPLETED
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Jonathan Hurley created AMBARI-11939:
----------------------------------------

             Summary: Upgrades Placed Into ABORTED Status Show As COMPLETED
                 Key: AMBARI-11939
                 URL: https://issues.apache.org/jira/browse/AMBARI-11939
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.1.0


When placing a stack upgrade request into the ABORTED state, Ambari calculates the stages and overall request as COMPLETED even though the tasks are actually ABORTED.

This prevents that request from being placed back into the PENDING state.

{code}

- Now this upgrade can be aborted:
{code:title=PUT api/v1/clusters/<cluster>/upgrades/21}
{
  "Upgrade": {
    "request_status": "ABORTED"
  }
}
{code}

- At this point, experimental mode can be enabled to work with Ambari. When finalize is ready, the same upgrade/request can be placed back into a {{PENDING}} status:
{code:title=PUT api/v1/clusters/<cluster>/upgrades/21}
{
  "Upgrade": {
    "request_status": "PENDING"
  }
}
{code}



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