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

Hadoop QA commented on AMBARI-19683:
------------------------------------

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

This message is automatically generated.

> Content of yarn-env.sh on host is not same as in the downloaded config file 
> from Ambari UI
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19683
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19683
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Dhanya Balasundaran
>            Assignee: Attila Magyar
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19683_branch-2.5.patch, AMBARI-19683_trunk.patch
>
>
> - Navigate to yarn services page
> - Download client config from Service Actions menu
> - Compare the contents in the downloaded file and in the yarn-env.sh on the 
> host
> - Two properties that differs are :
> - HADOOP_YARN_HOME
> - YARN_OPTS



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to