[
https://issues.apache.org/jira/browse/AMBARI-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999031#comment-14999031
]
Hadoop QA commented on AMBARI-13813:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12771555/AMBARI-13813-trunk.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 1 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/4243//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4243//console
This message is automatically generated.
> After kerberization, Kafka brokers fail to start
> ------------------------------------------------
>
> Key: AMBARI-13813
> URL: https://issues.apache.org/jira/browse/AMBARI-13813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade, stacks
> Affects Versions: 2.1.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13813-trunk.patch
>
>
> PROBLEM: After Ambari upgrade and kerberization, Kafka broker does not come
> up. Following error is observed:
> FATAL Fatal error during KafkaServer startup. Prepare to shutdown
> (kafka.server.KafkaServer)
> java.lang.IllegalArgumentException: You must pass
> java.security.auth.login.config in secure mode.
> STEPS TO REPRODUCE: Upgrade Ambari to 2.1.2 on a cluster without
> kerberization and with Kafka brokers, then kerberize through Ambari.
> EXPECTED RESULT: Kafka broker comes up successfully, and ambari sets the
> correct parameters in kafka-env.sh:
> {code}
> export
> KAFKA_KERBEROS_PARAMS="-Djava.security.auth.login.config=/etc/kafka/conf/kafka_jaas.conf"
>
> {code}
> ACTUAL RESULT: Kafka broker fails to come up and ambari-server set kafka-env
> incorrectly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
