[
https://issues.apache.org/jira/browse/AMBARI-21275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075612#comment-16075612
]
Hadoop QA commented on AMBARI-21275:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12873430/kafka.py.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11720//console
This message is automatically generated.
> Kafka advertised.listeners can't be configured when security is enabled
> -----------------------------------------------------------------------
>
> Key: AMBARI-21275
> URL: https://issues.apache.org/jira/browse/AMBARI-21275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
> Affects Versions: 2.4.2
> Reporter: Axton Grams
> Labels: kafka
> Fix For: trunk
>
> Attachments: kafka.py.patch
>
>
> When running Kafka Broker on a multi-homed, secure (kerberized) host, it is
> necessary to set the following configuration parameters:
> advertised.listeners=PLAINTEXTSASL://host.domain.tld:6667
> listeners=PLAINTEXTSASL://0.0.0.0:6667
> This configuration is not achievable due to limitations of the Ambari Server
> scripts that generate the Kafka Broker configuration file.
> The attached patch corrects this issue. The patch does a few things:
> - maintains consistency in behavior in updating protocol in
> advertised.listeners to match the behavior of existing parameter, 'listeners'
> - sets advertised.listeners to the listeners if it is not defined in Ambari
> - replaces the literal 'localhost' with the actual hostname; this is
> consistent with the behavior of the existing parameter, 'listeners'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
