signers timed out on canaries waiting on GS |
|||||||||
Issue description
These release builds failed:
relm/808
terra/811
banon/807
auron_yuna/806
The relm build failed after attempting for 2 hours to download a GS file:
01:28:22: INFO: RunCommand: /b/cbuild/internal_master/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-releases/canary-channel/relm/9234.0.0/ChromeOS-recovery-R58-9234.0.0-relm.instructions.json
01:28:22: INFO: RunCommand: /b/cbuild/internal_master/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-releases/dev-channel/relm/9234.0.0/ChromeOS-recovery-R58-9234.0.0-relm.instructions.json
...
03:28:08: INFO: RunCommand: /b/cbuild/internal_master/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-releases/dev-channel/relm/9234.0.0/ChromeOS-recovery-R58-9234.0.0-relm.instructions.json
03:28:08: ERROR: Image signing timed out.
,
Jan 30 2017
Per dgarrett, assign to vapier/davidriley to triage why signers are timing out.
,
Jan 30 2017
Theres reports that two signing hosts (chromeos-signing20.eem.corp.google.com and chromeos-signing21.eem.corp.google.com) which might be related.
,
Jan 31 2017
,
Feb 2 2017
We saw another round of this on the 2/1 canaries, were those signing hosts still having issues?
,
Feb 2 2017
the ACLs were broken last nite which caused all signers to fail. i'd ignore any signing failures in that time frame.
,
Feb 6 2017
,
Feb 6 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
,
Jun 21 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by semenzato@chromium.org
, Jan 30 2017