You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Xi Wang (JIRA)" <ji...@apache.org> on 2015/10/27 23:29:27 UTC

[jira] [Commented] (AMBARI-13593) Upgrade: UI should determine the ongoing skip failure flag based on Upgrade/skip_failures from the API

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

Xi Wang commented on AMBARI-13593:
----------------------------------

 10093 tests complete (13 seconds)
  105 tests pending

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