[
https://issues.apache.org/jira/browse/AMBARI-12927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723946#comment-14723946
]
Hadoop QA commented on AMBARI-12927:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12753158/AMBARI-12927.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServiceComponentTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3678//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3678//console
This message is automatically generated.
> Robustness of Stack Advisor to handle missing configs and others.
> -----------------------------------------------------------------
>
> Key: AMBARI-12927
> URL: https://issues.apache.org/jira/browse/AMBARI-12927
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.1
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.1.2
>
> Attachments: AMBARI-12927.patch
>
>
> Currently errors in the stack-advisor code during recommendations or
> validations blocks user from saving the configs. This is problematic where
> the user has to resort to pure API interaction.
> Ambari should be robust to tolerate any issues in the stack-advisor and still
> allow user to save configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
