New issue
Advanced search Search tips

Issue 855309 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Fix swarming auth to give all CI team members necessary privs

Project Member Reported by dgarr...@chromium.org, Jun 22 2018

Issue description

Something is wrong with the swarming permissions. Figure out which group is relevant, and add the CI team.
 
Owner: mikenichols@chromium.org
Status: Assigned (was: Untriaged)
Mike, this is in the bots.cfg that you're already modifying for the PreCQ allocation. One line change. Can you do this while you're there?
It's almost certainly, some group here:

https://chrome-infra-auth.appspot.com/auth/groups/build-internal-master-owners

And bots.cfg or something probably says which group.
Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 9

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/5bd054c721b7c47522f12fbcf75aaf2cdab18335

commit 5bd054c721b7c47522f12fbcf75aaf2cdab18335
Author: Mike Nichols <mikenichols@chromium.org>
Date: Mon Jul 09 17:51:36 2018

Status: Fixed (was: Started)
This should now be fixed.  

Updating permissions requires:

- Setting the proper MDB group in pools.cfg
- Ensuring that MDB group exists in ACL config.yaml(http://cl/203827387)

-- Mike

Sign in to add a comment