[
https://issues.apache.org/jira/browse/AMBARI-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18120:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit dc14815f13c465f6da7898c4b42a1fe63e8bb0ff
Author: Robert Levas <[email protected]>
Date: Thu Aug 11 17:06:51 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit dbf5aad2631ee67f2b859f85062bd3ec1bd34246
Author: Robert Levas <[email protected]>
Date: Thu Aug 11 17:07:43 2016 -0400
{noformat}
> Ambari upgrade to Ambari 2.4.0.0 did not change the krb5.conf template
> ----------------------------------------------------------------------
>
> Key: AMBARI-18120
> URL: https://issues.apache.org/jira/browse/AMBARI-18120
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18120_branch-2.4_01.patch,
> AMBARI-18120_trunk_01.patch
>
>
> After the successfully upgrading from Ambari 2.2.2 to Ambari 2.4.0, the
> krb5.conf template remained unchanged. As per AMBARI-13240, the template
> should get updated automatically after upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
