ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Khare (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-22356) Ambari changing kafka config upon regenerating keytabs
Date Thu, 02 Nov 2017 18:53:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-22356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arpit Khare updated AMBARI-22356:
---------------------------------
    Environment: 
Operating System: CentOS-7 (64 Bit)
Ambari Version: 2.5.2.0

  was:
Operating System: CentOS-6 (64 Bit)
Ambari Version: 2.5.2.0


> Ambari changing kafka config upon regenerating keytabs
> ------------------------------------------------------
>
>                 Key: AMBARI-22356
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22356
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>         Environment: Operating System: CentOS-7 (64 Bit)
> Ambari Version: 2.5.2.0
>            Reporter: Arpit Khare
>            Priority: Major
>         Attachments: compare_config.png
>
>
> In a Kerberos secure environment, when we add a property *security.inter.broker.protocol*
in custom kafka-broker from Ambari:
> {code}security.inter.broker.protocol = SASL_SSL{code}
> and we regenerate the keytabs for missing hosts and components, then Ambari overrides
this custom property and set it to the default value: 
> {code}security.inter.broker.protocol = PLAINTEXTSASL{code}
> Attachments:
> 1. Kafka Config compare screenshot: [^compare_config.png]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message