Closed
Bug 1333394
Opened 9 years ago
Closed 9 years ago
beetmover-build bustage Chain of Trust verification error!
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cbook, Assigned: jlorenzo)
References
()
Details
Attachments
(3 files)
Hit m-c a lot in https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=8ff550409e1d1f8b54f6f7f115545dbef857be0b
like https://tools.taskcluster.net/task-inspector/#MWv-OuoGQr-SCcAKuR8TCg/0
2017-01-24T12:08:23 INFO - Verifying beetmover:decision GaKA95I9Rh-VueTOv88aMA command...
2017-01-24T12:08:23 INFO - Verifying beetmover:build M9i2dRuBTtCuRl5Jde4f_A as a build task...
2017-01-24T12:08:23 INFO - Verifying beetmover:build:docker-image K6gdd6uVT2aFlPi-TlRBsQ as a docker-image task...
2017-01-24T12:08:23 CRITICAL - gecko-images is not a valid docker-image workerType!
2017-01-24T12:08:23 CRITICAL - Chain of Trust verification error!
Traceback (most recent call last):
File "/builds/scriptworker/lib/python3.5/site-packages/scriptworker/cot/verify.py", line 1219, in verify_chain_of_trust
task_count = await verify_task_types(chain)
File "/builds/scriptworker/lib/python3.5/site-packages/scriptworker/cot/verify.py", line 1027, in verify_task_types
await valid_task_types[task_type](chain, obj)
File "/builds/scriptworker/lib/python3.5/site-packages/scriptworker/cot/verify.py", line 927, in verify_docker_image_task
raise_on_errors(errors)
File "/builds/scriptworker/lib/python3.5/site-packages/scriptworker/cot/verify.py", line 200, in raise_on_errors
raise CoTError("\n".join(errors))
scriptworker.exceptions.CoTError: 'gecko-images is not a valid docker-image workerType!'
Updated•9 years ago
|
Component: General → Buildduty
Flags: needinfo?(rail)
Flags: needinfo?(bugspam.Callek)
Flags: needinfo?(aki)
Product: Taskcluster → Release Engineering
QA Contact: bugspam.Callek
| Reporter | ||
Comment 1•9 years ago
|
||
moving to blocker since this hit a lot of tier-1 jobs
Severity: normal → blocker
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jlorenzo
| Assignee | ||
Comment 2•9 years ago
|
||
I'm not sure, but I'm under the impression the image renaming that happened 2+ weeks ago (bug 1320328) hit production. I'm double-checking that with :dustin on IRC.
If I'm correct, this simple fix in scriptworker should do it.
| Assignee | ||
Comment 3•9 years ago
|
||
> 15:33:01 <•garndt> jlorenzo: the worker type name change landed on m-c on the 7th,
> so it's been using it since then at least there. It's possible that a new image was
> built on m-c recently and that's why cot is just now seeing it
Per [1], no image build occurred between Jan 7th and yesterday. This is very likely caused by the fact we didn't make the changes of bug 1320328 in scriptworker.
Clearing NI's and asking :jlund for a review.
[1] https://tools.taskcluster.net/index/artifacts/#docker.images.v2.level-3.desktop-build.pushdate.2017/docker.images.v2.level-3.desktop-build.pushdate.2017
Flags: needinfo?(rail)
Flags: needinfo?(bugspam.Callek)
Flags: needinfo?(aki)
| Assignee | ||
Updated•9 years ago
|
Attachment #8829848 -
Flags: review?(jlund)
| Assignee | ||
Comment 4•9 years ago
|
||
Attachment #8829886 -
Flags: review?(aki)
| Assignee | ||
Comment 5•9 years ago
|
||
First PR (attachment 8829848 [details] [review]) landed in master at: https://github.com/mozilla-releng/scriptworker/commit/c5d6856a85f78ed5968c35faf845b017f858ebdc
Waiting for review aki's review to validate the newly created v1 branch.
Updated•9 years ago
|
Attachment #8829886 -
Flags: review?(aki) → review+
| Assignee | ||
Comment 6•9 years ago
|
||
Second PR landed in v1 branch at https://github.com/mozilla-releng/scriptworker/commit/59bc81df05094829ce5fae0b92fbd2eff31d4bac.
Scriptworker 1.0.0b8 released: https://github.com/mozilla-releng/scriptworker/releases/tag/1.0.0b8
| Comment hidden (mozreview-request) |
| Assignee | ||
Comment 8•9 years ago
|
||
:aki told me mozreview is slow and he r+'d the puppet patch. That's now landed on the default branch at: https://hg.mozilla.org/build/puppet/rev/568772053921da04ed3fa0ed1bb61c49630ff2ec
Aki updated the production branch at: https://hg.mozilla.org/build/puppet/rev/2acccb11d9bf . The scriptworker instances should be updated within 30 minutes.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 9•9 years ago
|
||
| mozreview-review | ||
Comment on attachment 8829907 [details]
Bug 1333394 - Upgrade to scriptworker 1.0.0b8
https://reviewboard.mozilla.org/r/106870/#review107914
Attachment #8829907 -
Flags: review?(aki) → review+
Comment 10•9 years ago
|
||
I retriggered a beetmover job, and it went green. Triggered new nightlies on m-c.
Comment 11•9 years ago
|
||
Comment on attachment 8829848 [details] [review]
scriptworker PR
forgot to clear the review here after github. sigh.
Attachment #8829848 -
Flags: review?(jlund) → review+
Updated•8 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•