[
https://issues.apache.org/jira/browse/AMBARI-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866930#comment-15866930
]
Hadoop QA commented on AMBARI-19996:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852624/AMBARI-19996.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/10576//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10576//console
This message is automatically generated.
> Perform kinit on Kafka Start
> ----------------------------
>
> Key: AMBARI-19996
> URL: https://issues.apache.org/jira/browse/AMBARI-19996
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Attachments: AMBARI-19996.PATCH
>
>
> Perform Kinit with kafka keytab on Kafka broker start.
> As Kafka Client uses the cached kerberos ticket, so when kafka console
> commands like producer, consumer are run with kafka user and cluster is
> kerberoized, kinit should happen automatically
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
