[jira] [Commented] (AMBARI-17629) AUTH_TO_LOCAL rules are not updated when adding services to a Blueprint-installed cluster

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

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

Hadoop QA commented on AMBARI-17629:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12817995/AMBARI-17629_trunk_03.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/7844//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7844//console

This message is automatically generated.

> AUTH_TO_LOCAL rules are not updated when adding services to a Blueprint-installed cluster
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17629
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17629
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: auth_to_local, kerberos
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17629_branch-2.4_01.patch, AMBARI-17629_branch-2.4_02.patch, AMBARI-17629_branch-2.4_03.patch, AMBARI-17629_trunk_01.patch, AMBARI-17629_trunk_02.patch, AMBARI-17629_trunk_03.patch
>
>
> When adding new services and components to a cluster that was initially created via Blueprints (rather than via the Ambari UI), auth-to-local rules that are expected to be created as indicated by the Kerberos descriptor are not.
> It occurs because the components being installed are in the {{INIT}} state where the logic to determine whether to include the new auth-to-local rules or not expects the components to be in either the {{INSTALLED}} or {{STARTED}} states. This is due to logic added when resolving AMBARI-14232.
> *Solution*:
> Allow for auth-to-local rules for new services and components to be added when the state of the components are  {{INIT}} as well as {{INSTALLED}} and {{STARTED}}, when the cluster was installed via Blueprints. 



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