1516263 - Retriggers failing because of missing scope project:releng:beetmover:bucket:nightly

Status: RESOLVED WONTFIX

(Release Engineering :: Release Automation, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

https://tools.taskcluster.net/groups/XSbwpMLkSF6VhR_mNRJ8GA/tasks/cb43eraVT6KOpSf-tE3Syg/runs/0/logs/public%2Flogs%2Flive.log

It's a long error, but the beginning says

[task 2018-12-24T06:47:33.814Z] Client ID task-client/cb43eraVT6KOpSf-tE3Syg/0/on/us-east-1/i-06256b425be056204/until/1545635138.085 does not have sufficient scopes and are missing the following scopes:
[task 2018-12-24T06:47:33.814Z] 
[task 2018-12-24T06:47:33.814Z] ```
[task 2018-12-24T06:47:33.814Z] project:releng:beetmover:bucket:nightly
[task 2018-12-24T06:47:33.814Z] ```
[task 2018-12-24T06:47:33.814Z] 
[task 2018-12-24T06:47:33.814Z] You have the scopes:
[task 2018-12-24T06:47:33.814Z] 
[task 2018-12-24T06:47:33.814Z] ```

The task being retriggered was
  https://taskcluster-web.netlify.com/tasks/NZk8mhzHRwyNxJ34-Ljzqg
  beetmover-checksums-my-linux-nightly/opt
which was part of the nightly-desktop cron job.

So basically, that cron job has scopes that the "retrigger" action does not.  Options:
 * don't try to retrigger these jobs because it doesn't work
 * give the scope to the retrigger action (meaning anyone L3 can use the scope)
 * create a custom action for retriggering these tasks, that does not use the scope
 * .. probably more

Comment 1

[Aki Sasaki (not active)]

We probably don't want to retrigger these; we likely want to rerun them. However, we probably need to still fix scopes for rerunning.

Comment 2

[Aki Sasaki (not active)]

(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #1)

We probably don't want to retrigger these; we likely want to rerun them.

+1, https://docs.mozilla-releng.net/en/latest/taskcluster/rerun_vs_retrigger.html#deadline-exceeded-leaf-node-release-tasks
We tried retriggers recently and they had more problems than solutions.

Scopes are broken because we only grant these scopes to the relpro action instead of the retrigger action. We could address this, but given the above point about wanting reruns or custom relpro rather than retriggers, let's wontfix.