Issue metadata
Sign in to add a comment
|
signers can't access files uploaded to gs://chromeos-releases/ |
||||||||||||||||||||||||
Issue descriptiondon't know what changed, but looks recent (like last few hours). signers are all now failing with: 020217 07:48 DEBUG: RunCommand: /cros/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-releases/tobesigned/50,canary-channel,whirlwind,9202.13.0,ChromeOS-recovery-R57-9202.13.0-whirlwind.instructions 020217 07:48 DEBUG: (stderr): AccessDeniedException: 403 020217 07:48 WARNING: GS_ERROR: AccessDeniedException: 403 or something like: # /cros/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' stat -- gs://chromeos-releases/dev-channel/arkham/9202.13.0/ChromeOS-recovery-R57-9202.13.0-arkham.instructions You aren't authorized to read gs://chromeos-releases/dev-channel/arkham/9202.13.0/ChromeOS-recovery-R57-9202.13.0-arkham.instructions - skipping No URLs matched: gs://chromeos-releases/dev-channel/arkham/9202.13.0/ChromeOS-recovery-R57-9202.13.0-arkham.instructions
,
Feb 2 2017
What GS account is their .boto file tied too? I made some project level changes last night, which *should* have been innocent.
,
Feb 2 2017
Also, I undid my changes about 1 AM last night.
,
Feb 2 2017
,
Feb 2 2017
There was an acceptance step needed that has just been completed. So... in theory, this is fixed. I'm running paygen_payload_lib_unittest --network (which talks to the signers) to confirm this fix.
,
Feb 2 2017
the signers seem to be processing requests now, so i think it's all set |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by akes...@chromium.org
, Feb 2 2017