[jira] [Commented] (AMBARI-22016) changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-22016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189651#comment-16189651 ] 

Hadoop QA commented on AMBARI-22016:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12890141/AMBARI-22016_branch-2.6.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12408//console

This message is automatically generated.

> changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22016
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22016
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.5.2
>         Environment: Using Centos as the test bed
>            Reporter: Aman Poonia
>            Assignee: Aman Poonia
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-22016_branch-2.6.patch, AMBARI-22016.patch
>
>
> changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
> Currently we are doing 
> {code:java}
> function find_available_uid() {
>  for ((i=1001; i<=2000; i++))
>  do
>    grep -q $i /etc/passwd
>    if [ "$?" -ne 0 ]
>    then
>     newUid=$i
>     break
>    fi
>  done
> }
> {code}
> This will only check local user. Network manged users are not directly present inside passwd file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)