Issue metadata
Sign in to add a comment
|
chromeos_daisy_chromium_compile_only_ng builder GS ERROR |
||||||||||||||||||||||||
Issue descriptionFAILURE: https://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_chromium_compile_only_ng/builds/378625 OUTPUT: 16:29:56: WARNING: GS_ERROR: AccessDeniedException: 403 Caller does not have storage.objects.list access to bucket chromeos-image-archive. 16:29:56: ERROR: cros chrome-sdk failed before completing. 16:29:56: ERROR: return code: 1; command: /b/c/b/chromeos_daisy_chromium_compile_only_ng/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-image-archive/daisy-full/LATEST-9733.0.0 AccessDeniedException: 403 Caller does not have storage.objects.list access to bucket chromeos-image-archive. cmd=['/b/c/b/chromeos_daisy_chromium_compile_only_ng/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil', '-o', 'Boto:num_retries=10', 'cat', u'gs://chromeos-image-archive/daisy-full/LATEST-9733.0.0'], extra env={'BOTO_CONFIG': '/b/build/site_config/.boto'} step returned non-zero exit code: 1 BUILDSLAVE: https://build.chromium.org/p/tryserver.chromium.linux/buildslaves/slave802-c4 The failure was triggered when attempting to uprev the CrOS version for Simple Chrome. This causes the builder to download a new tarball from GS: https://chromium-review.googlesource.com/c/568527/ A similar builder succeeded: https://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-generic_chromium_compile_only_ng/builds/378441
,
Jul 13 2017
Depends how toolchain is installed, I suppose. The error in #0 looks like a Google Storage permissions issue, either with missing credentials on the bot or with "gsutil" not using the right credentials. Not sure which. #1 looks like a completely independent problem, although if there is a larger Google Storage bucket permissions issue then it might be related if the toolchain is loaded via GS. Adding actual owners of these systems.
,
Jul 13 2017
the file in question doesn't exist. it's come up before that GS is a bit weird that trying to read a file that doesn't exist hits a diff ACL (listing perms). so this specific failure is a symptom of a diff problem. looks like the LATEST files are out of sync and we need a refresh/reset here.
,
Jul 18 2017
,
Jul 18 2017
I think that https://chromium-review.googlesource.com/#/c/535847/ may be why the error message was different on the builder vs my local machine, thanks for pointing that out. The root cause of this was issue 741951 . I could probably improve the error message (the 'AccessDeniedException' is confusing), but given the current backlog I'm just going to close this as a duplicate. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by steve...@chromium.org
, Jul 13 2017Note: The change also fails locally also with --board=daisy --use-external-config, but the error message is different: 17:09:22: INFO: RunCommand: /usr/local/google/home/stevenjb/Work/chrome/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-image-archive/daisy-full/LATEST-9733.0.0 17:09:23: ERROR: cros chrome-sdk failed before completing. cros: Unhandled exception: ...python stack... raise MissingSDK(self.board, version) chromite.cli.cros.cros_chrome_sdk.MissingSDK: Cannot find SDK for 'daisy' with version 9733.0.0 Filed issue 741951 to track that issue. It is possible that the waterfall builder is giving a different / incorrect error for the same problem.