[
https://issues.apache.org/jira/browse/AMBARI-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701752#comment-14701752
]
Hadoop QA commented on AMBARI-12808:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12751030/AMBARI-12808.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 1 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.api.handlers.UpdateHandlerTest
org.apache.ambari.server.api.resources.BaseResourceDefinitionTest
org.apache.ambari.server.api.handlers.DeleteHandlerTest
org.apache.ambari.server.controller.internal.JMXHostProviderTest
org.apache.ambari.server.api.TestSuite
org.apache.ambari.server.api.handlers.CreateHandlerTest
org.apache.ambari.server.controller.AmbariManagementControllerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3606//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3606//console
This message is automatically generated.
> Ambari should not reset UIDs for existing users in a cluster
> ------------------------------------------------------------
>
> Key: AMBARI-12808
> URL: https://issues.apache.org/jira/browse/AMBARI-12808
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.1.2
>
> Attachments: AMBARI-12808.patch
>
>
> If a user wishes to set the UIDs for the users in an HDP cluster, due to some
> internal security requirements or standards, problems with rolling upgrades
> can occur, since the upgrade process will create files and directories with a
> UID of "1001" for "ambari-qa", even if the user had already set the UID for
> this user to a different value.
> The setup_users() method in the following stack script:
> ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py
> will always override the UID of a given cluster user, even if the customer
> has already customized this.
> The shared initialization scripts should check to see if a user has already
> been created with a separate UID, and provide a way to skip the process of
> setting the new UID. The Ambari scripts set the UID in order to comply with
> Hadoop and Kerberos standards, so any attempt to override this behavior
> should provide some config logging
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
