ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17629) AUTH_TO_LOCAL rules are not updated when adding services to a Blueprint-installed cluster
Date Fri, 15 Jul 2016 03:13:20 GMT


Hudson commented on AMBARI-17629:

SUCCESS: Integrated in Ambari-trunk-Commit #5311 (See [])
AMBARI-17629. AUTH_TO_LOCAL rules are not updated when adding services (rlevas: [])
* ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/
* ambari-server/src/main/java/org/apache/ambari/server/controller/
* ambari-server/src/main/java/org/apache/ambari/server/topology/
* ambari-server/src/main/java/org/apache/ambari/server/controller/
* ambari-server/src/test/java/org/apache/ambari/server/controller/
* ambari-server/src/test/java/org/apache/ambari/server/topology/
* ambari-server/src/main/java/org/apache/ambari/server/controller/

> AUTH_TO_LOCAL rules are not updated when adding services to a Blueprint-installed cluster
> -----------------------------------------------------------------------------------------
>                 Key: AMBARI-17629
>                 URL:
>             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,
> 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
> *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

View raw message