-
Notifications
You must be signed in to change notification settings - Fork 32
Restricted role satellite user #81
Comments
I think I found it. We were lacking the (my planned slot for this is CW44 but I might have a got at it during my vacation in CW40) @nstrug next hackathon sould be all day, we were so close. :-) logs from our attempt on with this user
using this role
we got
hammer itself is usable by the jenkins user
But
I have just granted the user that permission and was able to
|
this will take a few iterations to get the complete list of permissions from production.log, next failure is when the scripts try to delete kickstarts. |
note to self: |
That make sense since we have "--organization" in every hammer command. (I didn't see the error because I had set organization default on the system I tested the user on). May I suggest that you test the user and role creation with this script below? Then when all filters are correct, it can be used when setting up the environment as well.
For debugging, delete and recreate:
|
@ture-karlsson yeah, it's on my list of things to look at in CW44 (in addition to the issues I own) but this is your issue ;-) feel free to submit your results before that. If you have no setup you can test with, then assign this issue to me (well and grab me in internal IRC next week so that we can make sure you somehow get your own test setup) |
Yes, I haven't found any time to work on this yet, sorry. |
note to self: my current WIP role is as follows
|
We need to restrict the role of the satellite jenkins user to minimum permissions required for running the job.
The text was updated successfully, but these errors were encountered: