[
https://issues.apache.org/jira/browse/AMBARI-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974945#comment-14974945
]
Hudson commented on AMBARI-13563:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #748 (See
[https://builds.apache.org/job/Ambari-branch-2.1/748/])
AMBARI-13563 Upgrade: UI should determine the ongoing upgrade type based
(atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4a4d8d09eddf7eb10a45989c614e48055dd14af4])
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/controllers/global/cluster_controller.js
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
> Upgrade: UI should determine the ongoing upgrade type based on
> Upgrade/upgrade_type from the API
> ------------------------------------------------------------------------------------------------
>
> Key: AMBARI-13563
> URL: https://issues.apache.org/jira/browse/AMBARI-13563
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13563.patch
>
>
> Currently, we are using localDB/persist to rely on what the upgrade type
> (ROLLING vs NON_ROLLING) is. This should be changed now that GET on the
> upgrade endpoint provides this info, since relying on localDB/persist can be
> unreliable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
