[
https://issues.apache.org/jira/browse/AMBARI-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707200#comment-14707200
]
Hudson commented on AMBARI-12808:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #407 (See
[https://builds.apache.org/job/Ambari-branch-2.1/407/])
AMBARI-12808 Ambari should not reset UIDs for existing users in a cluster
(dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=de90bce91aeddd85efdd5f9bafa45cca803c362d)
* ambari-server/src/test/python/stacks/2.0.6/configs/default.json
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog212.java
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog212Test.java
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py
* ambari-web/app/utils/config.js
* ambari-web/app/data/HDP2/site_properties.js
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml
*
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-env.xml
> 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-2.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)
