ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16704) UI - RU/EU, when initiating a downgrade, should ensure that request to ABORT upgrade returns 200
Date Tue, 17 May 2016 19:22:12 GMT

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

Hudson commented on AMBARI-16704:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #4859 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4859/])
AMBARI-16704 UI - RU/EU, when initiating a downgrade, should ensure that (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1893d15f9ee2faff2ad680daa27208aa752ef081])
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js


> 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)

Mime
View raw message