New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 863140 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

nativeclient.bot@gmail.com needs write permission in nativeclient-archive2

Project Member Reported by thomasanderson@chromium.org, Jul 12

Issue description

The latest runs on client.nacl.toolchain are failing because the bots cannot upload the new nacl toolchains:

https://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_64/builds/6962
https://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_64/builds/6962/steps/upload_package_info/logs/stdio
AccessDeniedException: 403 nativeclient.bot@gmail.com does not have storage.objects.create access to nativeclient-archive2/builds/e6ce828ef60c4c1438867b535efbbb5d9a177c0e/win_x86/pnacl_newlib/compiler_rt_bc_arm_bc.tgz.json.tmp.ycvoridbpj.
T

Tentatively assigning to martiniss to fix or assign to someone who can.
 
Labels: Foundation-Troopers
Owner: ----
Status: Available (was: Assigned)
I couldn't find that bucket in the chromium-archive project, and I'm not sure where it comes from.

I think that Foundation deals with this stuff? Adding to their queue, let me know if you need any help with it.
Labels: -Foundation-Troopers
I also have no idea in what project nativeclient-archive2 bucket is. And I have no permissions to modify its ACL. It appears this bucket wasn't created by Chrome Infra and we can't modify its permissions. 

I'm sorry, we can't help with this request. You'll need to find who owns this bucket or who set it up in the first place. 
Cc: mseaborn@chromium.org dschuff@chromium.org sbc@chromium.org
+nacl folks

Cc: bradnelson@chromium.org
Brad, do you know who has the ability to modify the ACL for the bucket nativeclient-archive2?
Owner: dschuff@chromium.org
Hi myself, nacl-eng@, dschuff@, hinoka@, gdeepti@, binji@ have (and several others) have access.

nativeclient.bot@gmail.com appeared to have "viewer" access only.
I've changed it to "Editor", however, note there is are a number of other service accounts with edit access and I believe at one point those accounts were what the bots used for uploads. My impression since is that for chromium these have moved to a single shared owner etc. hinoka@ / iannucci@ would know best.

Thanks bradnelson, but the bot is still having troubles:

AccessDeniedException: 403 nativeclient.bot@gmail.com does not have storage.objects.create access to nativeclient-archive2/builds/aebc9e5205dcaad5d5954a18abc532316a954644/win_x86/pnacl_newlib/compiler_rt_bc_arm_bc.tgz.json.tmp.lhqclohovi.
Status: Assigned (was: Available)
Cc: -dschuff@chromium.org hinoka@chromium.org
hinoka@ and I are currently working on transitioning these bots to LUCI. So it probably makes sense to figure this out on the new infrastructure rather than the old (at which point I will need to better understand myself what the right way forward is).

Sign in to add a comment