-
Notifications
You must be signed in to change notification settings - Fork 35
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
Users are no longer added to existing groups since 1.0.4 #44
Comments
I can confirm this issue on Centos7 with 1.0.5. With a new image, the keymaker_groups get created on the server, but the users do not get added to them. Reverting to 1.0.3 solves the problem. |
Thank you both for reporting this. I just released v1.0.6 with a fix for a logic error that I introduced in v1.0.4. Could you please test v1.0.6 and see if your issue is resolved? If not, can you please tell me the following:
Thanks. |
Yes, this is working correctly for me on 1.0.6. |
Well maybe I spoke too soon. The first image I spun up worked perfectly. But the second one generated these errors on my first login: rscott@gtri-ubuntu:~/git/arfam-provision/ami$ hop 10.100.52.26 =========================================== keymaker:x:1001: [rscott@ip-10-10-10-10 ~]$ keymaker --version [rscott@ip-10-10-10-10 ~]$ keymaker get_groups rscott [rscott@ip-10-10-10-10 ~]$ keymaker sync_groups |
I think that the problem described above has to do with logging in for the first time before the first cron job has run to populate the groups. Since the groups have not yet populated, each attempt to add the user to the group fails. And then--apparently--it never tries to add the user again. I have verified that a new user logging in after the groups are first populated does get added to the groups, but the first guy who logged in too early is SOL. So the work-around for this issue as it now stands is to wait until after there's been enough time for the first cron job to run before logging in. |
@rscottthreewiresyscom thank you for clarifying. You are correct, and this is not a new issue: groups are created on demand by With that said, |
I'm having what appears to be the same issue.
I think it's caused by these lines of code:
If |
Thank you @georgebuckerfield. Merged your fix and released in v1.0.7. |
Great, thanks for the quick turnaround @kislyuk and thanks for maintaining keymaker, it's very useful! |
We use "keymaker_wheel" as our IAM group for admin users. Admin users are added to the local "wheel" group in version 1.0.3, but beginning with 1.0.4, that no longer happens.
I haven't tested to see if new groups (eg "keymaker_notwheel") would be created successfully and users added.
The text was updated successfully, but these errors were encountered: