You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2017/03/20 22:08:41 UTC

[jira] [Updated] (AMBARI-19473) Add Downgrade request validation to avoid accidental double-upgrades

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

Yusaku Sako updated AMBARI-19473:
---------------------------------
    Reporter: Vivek Sharma  (was: Jonathan Hurley)

> Add Downgrade request validation to avoid accidental double-upgrades
> --------------------------------------------------------------------
>
>                 Key: AMBARI-19473
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19473
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Vivek Sharma
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19473.patch
>
>
> There are currently several ways of starting upgrades / downgrades:
> - The use of a directive on the request
> {noformat}
> http://localhost:8080/api/v1/clusters/c1/upgrades?downgrade=true
> {noformat}
> - The POST body JSON
> {noformat}
> {
> "RequestInfo": {
>   "downgrade": "true"
>   },
> "Upgrade":{
>   "from_version": ...
>  }
> }
> {noformat}
> The directive is confusing and can allow multiple downgrades or upgrades to be scheduled concurrently. It should be removed for consistency and the {{Upgrade/direction}} property should replace it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)