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

Hadoop QA commented on AMBARI-17522:
------------------------------------

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

This message is automatically generated.

> Handle Ranger Kms upgrade in kerberos env
> -----------------------------------------
>
>                 Key: AMBARI-17522
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17522
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17522.patch
>
>
> *Problem*:
> Upgrade from 2.4 to 2.5 will not have rangerkms principal/keytab identity (as 
> it is added in stack 2.5) to create/get repository in Ranger Service.
> Ranger KMS service had spnego principal/keytab identity in 2.4.
> Ranger KMS service is a dependent on Ranger Service. For previous stack all 
> calls were using urllib2 authentication to create/get repository in Ranger 
> Service in kerberos env. Ranger Service participate in kerberos from 2.5 
> onwards so all call to create/get repository will be using curl --negotiate.



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

Reply via email to