[
https://issues.apache.org/jira/browse/AMBARI-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999293#comment-14999293
]
Hadoop QA commented on AMBARI-13818:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12771588/AMBARI-13818.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 1 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/4245//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4245//console
This message is automatically generated.
> SKIPPED_FAILED state should not be bubbled up to the Upgrade level
> ------------------------------------------------------------------
>
> Key: AMBARI-13818
> URL: https://issues.apache.org/jira/browse/AMBARI-13818
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.3
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13818.patch
>
>
> When there is a skipped failure, the "upgrade" state itself comes
> SKIPPED_FAILED. Even when the upgrade is running or paused, it is returning
> "SKIPPED_FAILED". The API should not roll this up to the "upgrade" level as
> the current behavior is confusing. At the top level, it should just be
> HOLDING, IN_PROGRESS, COMPLETED, etc. SKIPPED_FAILED should be bubbled up to
> the upgrade group level and stop there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
