[
https://issues.apache.org/jira/browse/AMBARI-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977688#comment-14977688
]
Hudson commented on AMBARI-13593:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3726 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3726/])
AMBARI-13593. Upgrade: UI should determine the ongoing skip failure flag
(xiwang:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=376f80fc20defbce8b369490a40f7f65fd2253da])
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/controllers/global/cluster_controller.js
> Upgrade: UI should determine the ongoing skip failure flag based on
> Upgrade/skip_failures from the API
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-13593
> URL: https://issues.apache.org/jira/browse/AMBARI-13593
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Xi Wang
> Assignee: Xi Wang
> Fix For: 2.1.3
>
> Attachments: AMBARI-13593.patch
>
>
> Currently, we are using localDB/persist to rely on Upgrade Options >
> skip_failures flags.
> 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)
