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