[
https://issues.apache.org/jira/browse/AMBARI-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821835#comment-15821835
]
Hadoop QA commented on AMBARI-19473:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847140/AMBARI-19473.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10032//console
This message is automatically generated.
> 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: Jonathan Hurley
> 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.4#6332)
