You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2015/01/02 15:30:13 UTC

[jira] [Resolved] (AMBARI-8852) RU: Cannot Retry on failure

     [ https://issues.apache.org/jira/browse/AMBARI-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Beerbower resolved AMBARI-8852.
-----------------------------------
    Resolution: Fixed

Looks like the revert was reverted by Dmitry.

> RU: Cannot Retry on failure
> ---------------------------
>
>                 Key: AMBARI-8852
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8852
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8852.patch
>
>
> During RU, a failure occurred on "Client Components" group, "Service Check HBASE, MAPREDUCE2, HDFS, YARN" item.
> The UI presented me with a Retry button.  However, the server rejected this request:
> PUT /api/v1/clusters/ysru2/upgrades/5/upgrade_groups/4/upgrade_items/30
> {"UpgradeItem":{"status":"PENDING"}}
> {
>   "status" : 400,
>   "message" : "java.lang.IllegalArgumentException: Can not transition a stage from FAILED to PENDING"
> }
> I believe this is the current expected behavior since the failure is not marked to hold.  
> However, on any service check failure, the user should be able to retry (or maybe on any failure?  actions should be idempotent).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)