[
https://issues.apache.org/jira/browse/AMBARI-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255468#comment-14255468
]
Hadoop QA commented on AMBARI-8852:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12688606/AMBARI-8852.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1047//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1047//console
This message is automatically generated.
> 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)
