You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/02/03 06:27:34 UTC

[jira] [Commented] (AMBARI-9360) Implement unkerberize for kerberized cluster

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

Hadoop QA commented on AMBARI-9360:
-----------------------------------

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

This message is automatically generated.

> Implement unkerberize for kerberized cluster
> --------------------------------------------
>
>                 Key: AMBARI-9360
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9360
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos, kerberos_descriptor
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9360_01.patch, AMBARI-9360_02.patch
>
>
> Implement the ability to disable Kerberos from a cluster that was previously configured for Kerberos.
> This entails reverting configuration properties set when Kerberos was enabled to default values found in the stack. 
> Principals will not be destroyed in the KDC and ketyab files will not be removed from hosts.



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