[
https://issues.apache.org/jira/browse/AMBARI-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563003#comment-14563003
]
Hadoop QA commented on AMBARI-11481:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735855/AMBARI-11481_01.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/2903//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2903//console
This message is automatically generated.
> Kerberos Descriptor removal failure during cleanup should not be critical
> -------------------------------------------------------------------------
>
> Key: AMBARI-11481
> URL: https://issues.apache.org/jira/browse/AMBARI-11481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Emil Anca
> Assignee: Emil Anca
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11481_01.patch
>
>
> When securing the cluster via API, there's no Kerberos Descriptor being
> persisted in the database. This causes de-Kerberization to fail. To fix this,
> failure to find the descriptor during cleanup should not be critical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
