Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 20 Oct 2015 15:54:27 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12906278.1445356438000.8578.1445356467860@Atlassian.JIRA>
In-Reply-To: <JIRA.12906278.1445356438000@Atlassian.JIRA>
References: <JIRA.12906278.1445356438000@Atlassian.JIRA>
 <JIRA.12906278.1445356438576@arcas>
Subject: [jira] [Created] (AMBARI-13491) Expose Failure Auto-Skip Setting On
 Upgrade Endpoint
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jonathan Hurley created AMBARI-13491:
----------------------------------------

             Summary: Expose Failure Auto-Skip Setting On Upgrade Endpoint
                 Key: AMBARI-13491
                 URL: https://issues.apache.org/jira/browse/AMBARI-13491
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 2.1.3
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.1.3


Upgrades can optionally be set to automatically skip slave/client failures and/or service check failures. This helps the upgrade process be more automated by requiring less interaction from administrators. 

These two optional preferences should be exposed via the upgrades endpoint on each upgrade:

{code:title=GET api/v1/clusters/c1/upgrades/92}
"Upgrade": {
"cluster_name": "c1",
"create_time": 1443818468162,
"direction": "UPGRADE",
"end_time": 1443876837814,
"exclusive": false,
"from_version": "2.2.7.0-2816",
"progress_percent": 75.00769822940724,
"request_context": "Upgrading to 2.3.0.0-2557",
"request_id": 92,
"request_status": "IN_PROGRESS",
"start_time": 1443818472898,
"to_version": "2.3.0.0-2557",
"type": "INTERNAL_REQUEST"
...
{code}

Two new options should be exposed here:
{code}
    "skip_failures": true,
    "skip_service_check_failures": true
{code}


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