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

Hadoop QA commented on AMBARI-17587:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12816582/AMBARI-17587.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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7714//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7714//console

This message is automatically generated.

> Handle post ambari upgrade scenario for real names of jdbc jar file[Ranger]
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-17587
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17587
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17587.patch
>
>
> Post Ambari upgrade nothing should break for Ranger and Ranger Plugin after  
> implementation of AMBARI-15628.



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

Reply via email to