[
https://issues.apache.org/jira/browse/AMBARI-16704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286668#comment-15286668
]
Hadoop QA commented on AMBARI-16704:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804423/AMBARI-16704.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6862//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6862//console
This message is automatically generated.
> UI - RU/EU, when initiating a downgrade, should ensure that request to ABORT
> upgrade returns 200
> ------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16704
> URL: https://issues.apache.org/jira/browse/AMBARI-16704
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.2
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16704.patch
>
>
> As part of AMBARI-15673, which was a back-end bug, we found that the UI would
> initiate a Downgrade by sending 2 separate requests.
> # ABORT the current upgrade
> # Create a request to begin the Downgrade
> At the time, #1 was failing with 400 code but the UI was still sending #2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
