-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
account for unique user group #664
base: master
Are you sure you want to change the base?
Conversation
use 'id -gn' to get the user group
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lattisimo Looks like the build is failing here https://app.circleci.com/pipelines/github/StackStorm/st2-packages/77/workflows/75cabd81-6e11-43dd-8c88-a8cce7ae7904/jobs/3628
Can you please update https://github.com/StackStorm/st2-packages/blob/master/scripts/st2bootstrap-el8.template.sh
Then run make scriptsgen
and include the changed files?
Thanks!
@lattisimo Would be good to know the more context around this issue: what led you to this solution, what's the issue, error message, etc. |
Since this is my first interaction of this sort. I want to follow up if there is any additional action needed on my part? I am not confident that I accomplished what @nmaludy has asked of me. |
@lattisimo Your changes look good, we're just in a change freeze right now due to a pending 3.3.0 release. I'm going to target this for the 3.4.0 milestone, does that sound good? |
Sounds good. Thanks. |
Shawn Robinson seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Use
id -gn
to get the user group forcurl|bash
stackstorm installer.The issue I had was installing on a box that had LDAP configured and my user group is 'domain users' since the script just assumed the group matched the user so the chown command fails and the script stops executing. I can avoid the issue by 'sudo su' but I realized that if I get the user's group with 'id -gn' then there is no assumption of what that value should be. This would likely be relevant on the other scripts.