ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-12808) Ambari should not reset UIDs for existing users in a cluster
Date Tue, 18 Aug 2015 13:12:45 GMT
Dmytro Sen created AMBARI-12808:
-----------------------------------

             Summary: 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)

Mime
View raw message