[
https://issues.apache.org/jira/browse/AMBARI-22016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214634#comment-16214634
]
Swapan Shridhar commented on AMBARI-22016:
------------------------------------------
[~mnpoonia] Is it fixed ? If yes, please close it, else move it to 2.6.1.
Reason : I have to start the release process for Ambari-2.6
Thx.
> 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.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
(v6.4.14#64029)
