Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 913CD18547 for ; Thu, 20 Aug 2015 18:42:46 +0000 (UTC) Received: (qmail 64121 invoked by uid 500); 20 Aug 2015 18:42:46 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 64090 invoked by uid 500); 20 Aug 2015 18:42:46 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 64075 invoked by uid 99); 20 Aug 2015 18:42:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Aug 2015 18:42:46 +0000 Date: Thu, 20 Aug 2015 18:42:46 +0000 (UTC) From: "Dmytro Sen (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-12808) Ambari should not reset UIDs for existing users in a cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-12808: -------------------------------- Attachment: AMBARI-12808-2.patch > 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)