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

Zack Marsh commented on AMBARI-12093:
-------------------------------------

I've tried modifying the Jinja2 template Ambari is using to create the 
krb5.conf file so that we can leave the check-box checked, and allow Ambari to 
manage the krb5.conf file.

After modifying the file: 
'/var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/templates/krb5_conf.j2',
 I restarted the Ambari Server, but I noticed the file 
'/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/templates/krb5_conf.j2'
 is not reflecting the changes, and the default krb5 template seen in the 
Enable Kerbreos Wizard also doesn't reflect the changes.

Is there a recommended way to patch this template file so the Kerberos Wizard 
uses the modified version?

> Enable Security Wizard not honoring the unchecking of the "Manage Kerberos 
> client krb5.conf" check box
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12093
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12093
>             Project: Ambari
>          Issue Type: Bug
>         Environment: ambari-2.1.0-1213, hdp-2.3.0.0-2450, sles11sp3
>            Reporter: Zack Marsh
>            Priority: Blocker
>
> In Ambari's Enable Kerberos Wizard, in the step “Configure Kerberos” there is 
> a check-box under “Advanced krb-conf” for “Manage Kerberos client krb5.conf". 
> We are generating our own krb5.conf file in our Kerberos setup script,  
> therefore we have been deselecting this check-box to prevent Ambari from 
> overwriting our changes.
> In the last several builds of Ambari/HDP some users (using Chrome and 
> Firefox) are finding that Ambari is not honoring un-checking this option, and 
> overwriting the krb4.conf file. This is resulting in many failures starting 
> services (Data Node and Journal Node) during the last step of the Kerberos 
> Wizard.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to