[
https://issues.apache.org/jira/browse/AMBARI-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956814#comment-14956814
]
Hadoop QA commented on AMBARI-13420:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12766468/AMBARI-13420.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/3965//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3965//console
This message is automatically generated.
> RU should check for INSTALL_FAILED components before starting
> --------------------------------------------------------------
>
> Key: AMBARI-13420
> URL: https://issues.apache.org/jira/browse/AMBARI-13420
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.2
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Fix For: 2.1.3
>
> Attachments: AMBARI-13420.patch
>
>
> Repro Steps:
> # Start RU with client components in INSTALL_FAILED state.
> # RU starts as there are no pre-req check that fails when components are in
> INSTALL_FAILED state.
> # However RU is aborted when upgrading components in INSTALL_FAILED state
> # This was because RU did not know how to handle upgrade of INSTALL_FAILED
> components
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
