[jira] [Commented] (AMBARI-13018) Upgrade API Endpoint Should Rely on Prerequisite Endpoint Before Running

["Jayush Luniya (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739751#comment-14739751 ] 

Jayush Luniya commented on AMBARI-13018:
----------------------------------------

Trunk
commit d4182e13d199be5a3870e3649088a3bd682f5bb3
Author: Jayush Luniya <jl...@hortonworks.com>
Date:   Thu Sep 10 15:30:24 2015 -0700

    AMBARI-13018: Upgrade API Endpoint Should Rely on Prerequisite Endpoint Before Running (jluniya)

> Upgrade API Endpoint Should Rely on Prerequisite Endpoint Before Running
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-13018
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13018
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>            Priority: Critical
>             Fix For: 2.1.2
>
>
> It is currently possible to execute an upgrade, bypassing the prerequisite endpoint checks entirely by using the upgrade endpoint API. For users that plan to use the APIs directly instead of the web client, this can present a problem if they have prerequisites for the upgrade that are not yet met.
> The upgrade endpoint should, by default, check the prerequisite endpoint to see if any checks have failed. If there is a failure, an error code should be returned and the upgrade will not begin. However, there can be an optional override to the API upgrade request to force the upgrade regardless of prerequisite checks:
> {code:title=POST api/v1/clusters/c1/upgrades}
> {
>   "Upgrade": {
>     "repository_version": "2.3.0.0-2545",
>     "skip_prerequisite_checks": true
>   }
> }
> {code}



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