-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hue user exists? #112
Comments
Thanks for the report! Here's the juicy part: File "/root/.local/pipx/venvs/isilon-hadoop-tools/lib/python3.8/site-packages/isilon_hadoop_tools/identities.py", line 259, in create_user
uid = self.onefs.uid_of_user(
File "/root/.local/pipx/venvs/isilon-hadoop-tools/lib/python3.8/site-packages/isilon_hadoop_tools/onefs.py", line 572, in _decorated
return func(self, *args, **kwargs)
File "/root/.local/pipx/venvs/isilon-hadoop-tools/lib/python3.8/site-packages/isilon_hadoop_tools/onefs.py", line 1277, in uid_of_user
return int(auth_users.users[0].uid.id.split(":")[1])
AttributeError: 'NoneType' object has no attribute 'id' The first line tells us the IHT correctly figured out that we got a "user already exists" error and tried to get the UID of the existing user (so that it could put the same UID into the client-side user-creation script).
That line has been there since the Python port was created. Given that:
I wonder if this is due to a change in a more recent version of OneFS 🤔
|
This was a physical cluster running 9.4 |
update: I knew it was hue related....there is a user called hue in AD and AD was added to that zone when i ran the script. So of course hue already existed. Just re-ran without AD joined and it worked just fine. Maybe make a note in the documentation to run beofore adding AD or LDAP to the AZ. |
Even though its a new access zone the script is failing with an error that user Hue exists. Some kind of a race condition? Please review
Evidence:
The text was updated successfully, but these errors were encountered: