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

Hudson commented on AMBARI-13813:
---------------------------------

ABORTED: Integrated in Ambari-branch-2.1 #839 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/839/])
AMBARI-13813 After kerberization, Kafka brokers fail to start (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b83506ed33a8cb9726dd56ed345fffd90c3986ad])
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
AMBARI-13813 After kerberization, Kafka brokers fail to start (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=26669facf0a3b5de22ae8bb48134e42ae604ab28])
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java


> 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)

Reply via email to