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

["Wei-Chiu Chuang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-22016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang updated AMBARI-22016:
-------------------------------------
    Fix Version/s: 3.1.0
                       (was: 3.0.0)

> 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
>            Priority: Major
>             Fix For: 3.1.0
>
>         Attachments: AMBARI-22016.patch, AMBARI-22016_branch-2.6.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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ambari.apache.org
For additional commands, e-mail: issues-help@ambari.apache.org