Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Duplicate
Merged: issue 688026
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: ----



Sign in to add a comment
lakitu-paladin failing with GS upload failure
Project Member Reported by uekawa@chromium.org, Feb 2 2017 Back to list
lakitu-paladin:5439 failed

Builders failed on: 
- lakitu-paladin: 
  https://luci-milo.appspot.com/buildbot/chromeos/lakitu-paladin/5439


https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin/builds/5440/steps/BuildPackages/logs/stdio

5440 failure 
04:22:32: WARNING: GS_ERROR: AccessDeniedException: 403 Caller does not have storage.objects.list access to bucket container-vm-image-staging.




 
Cc: ameyd@google.com
I guess it's gs://container-vm-image-staging which is probably owned by lakitu team, not sure why it's starting to fail.


04:22:32: ERROR: <class 'chromite.lib.gs.GSCommandError'>: return code: 1; command: /b/cbuild/internal_master/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' -m cp -v -- /b/cbuild/internal_master/buildbot_archive/lakitu-paladin/R58-9243.0.0-rc4/build-events.json gs://container-vm-image-staging/lakitu-paladin/R58-9243.0.0-rc4/build-events.json



Labels: OS-Chrome Pri-0
Mergedinto: 688026
Status: Duplicate
This appears to be fixed now, since the current build has gotten past the broken stage. Sorry about this!

https://luci-milo.appspot.com/buildbot/chromeos/lakitu-paladin/5445
Sign in to add a comment