[jira] [Commented] (AMBARI-18463) Regression: krb5JAASLogin.conf is not updated during secure BP install

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-18463:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12831156/AMBARI-18463_trunk_02.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8783//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8783//console

This message is automatically generated.

> Regression: krb5JAASLogin.conf is not updated during secure BP install
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-18463
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18463
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: blueprints, kerberos
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18463_branch-2.5_01.patch, AMBARI-18463_branch-2.5_02.patch, AMBARI-18463_trunk_01.patch, AMBARI-18463_trunk_02.patch
>
>
> When installing a secure cluster using Blueprints, Ambari's {{/etc/ambari-server/conf/krb5JAASLogin.conf}} is not updated to reflect the details of the Ambari Kerberos identity.
> This was introduced by the patch for AMBARI-18406.



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