Hide Forgot
Description of problem: Looking at a job view the Ack, Nak, comment options are not available on jobs submitted by other users. For example the my group review the kernel jobs from maintainers. The plan was to use Clone, Nak and comment in replace of recipes requeue. But if we can't set the Nak on other users jobs this workflow will not work.
Are you in the same group in Beaker as those who submit jobs you wish to ack/nak/comment on ?
Raymond, Yes we are in the kernel-mtr group. But I want to make sure I didn't add some confusion. When I used the word group I am was not referring to the Beaker group. I was just saying Paul, Jan and myself need to be able to set Ack, Nak, comments on other peoples jobs. Specifically the kernel maintainers. Of course if by using groups is how you would like to implement a resolution I think it may work. The additional thing we noticed on Friday is that individuals that have an email address that doesn't match their kerberos login name also can't set the Ack, Nak, comment on their own jobs. For example: email = jwilson kerberos = jarod Jarod can't Ack, Nak, comment on his own jobs. Thanks, Jeff
(In reply to comment #2) > Raymond, > Yes we are in the kernel-mtr group. But I want to make sure I didn't add some > confusion. When I used the word group I am was not referring to the Beaker > group. I was just saying Paul, Jan and myself need to be able to set Ack, Nak, > comments on other peoples jobs. Specifically the kernel maintainers. > > Of course if by using groups is how you would like to implement a resolution I > think it may work. > I guess it would be ideal if we could have at least some level of permissions on this feature. > The additional thing we noticed on Friday is that individuals that have an > email address that doesn't match their kerberos login name also can't set the > Ack, Nak, comment on their own jobs. For example: > email = jwilson > kerberos = jarod > > Jarod can't Ack, Nak, comment on his own jobs. > Oh interesting, will investigate > Thanks, > Jeff
Ray, Can we open this up for anyone to ack/nak anyone's job? Would it be possible to have this for the next release? 0.6.6? Thanks
As discussed with bpeck, create group level perms on this action. Those who need to have equal access to this will need to have a group created if one does not already exist.
Jeff, I can't see how Jarod could not have access to Ack/Nak his own jobs. I'm not really sure what's happening here. I can't find a Kerb user for 'jarod', and there is no 'jardon' in the beaker db. Only jwilson. What's his user name when he logs into beaker, and what's the user name associated with his jobs ?
Ray, Regarding comment#5. I believe having this ack/nak ability for members of the "kernel-mtr" group would sufffice. Thank you. -pbunyan
Hi Paul, It's being implemented in such a way that any common group member of any group of which the job owner belongs to, can do the ack/nak. That should keep it generic enough.