[ 
https://issues.apache.org/jira/browse/AMBARI-17296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336358#comment-15336358
 ] 

Hadoop QA commented on AMBARI-17296:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12811368/AMBARI-17296.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 2 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/7404//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7404//console

This message is automatically generated.

> Ambari displays a warning about config values not being at optimal values 
> right after a clean install with no customization
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17296
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17296
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17296.patch
>
>
> With nothing changed manually on a new install, Ambari displayed a message
> saying that certain configs are not at the recommended values.  
> Given this was a new install with no modifications - the values should have
> been populated by Ambari itself.
> I don't know what the final values was because the cluster install failed
> (likely due to repo issues)
> Attaching a screenshot.



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

Reply via email to