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

Hadoop QA commented on AMBARI-11685:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12737562/AMBARI-11685.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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/3030//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3030//console

This message is automatically generated.

> YARN repo in Ranger Admin neds to have the right value for YARN REST URL
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-11685
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11685
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11685.patch
>
>
> Ambari automation created YARN repo in Ranger Admin doesn't have the right 
> value for YARN REST URL
> Config doesn't have the required "http://"; scheme in it.



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

Reply via email to