1575243 - Can not retrigger a job on treeherder after taskcluster credentials expired in background

Status: RESOLVED INVALID

(Tree Management :: Treeherder, defect)

Description

[malikanshul29]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

I use my email id to run the try jobs and out of the 4 options to login in treeherder, i can only use the firefox account oauth. The email id on firefox account is same as the one I use to trigger the try jobs.

So, I triggered a try run https://treeherder.mozilla.org/#/jobs?repo=try&revision=b4df21ca05303436f8e70369fcfa7d5321771f59&selectedJob=262441778

Actual results:

Some tests failed and when I tried to retrigger the failed tests, i got this error:

Retrigger failed: Error: Client ID mozilla-auth0/oauth2|firefoxaccounts|199818047702495ab5f08a1bb0bd51e4|[e-mail] does not have sufficient scopes and is missing the following scopes: hooks:trigger-hook:project-gecko/in-tree-action-1-generic/d48859b560 This request requires the client to satisfy the following scope expression: hooks:trigger-hook:project-gecko/in-tree-action-1-generic/d48859b560

Expected results:

The tests should have retriggered

Comment 1

[Andrew Halberstadt [:ahal]]

It's possible this belongs in Firefox Build System :: Task Configuration rather than treeherder, but it's unclear from the description.

Comment 2

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Sometimes one is logged into Treeherder but the credentials for Taskcluster on which the tasks run has expired in the background. If it happens again, go to https://firefox-ci-tc.services.mozilla.com/ and sign out. Then also sign out of Treeherder and log in again. Does retriggering builds work after that?

Comment 3

[Sarah Clements [:sclements]]

This was filed before the Nov 9th Taskcluster switch to the new OAuth third party login. Treeherder retrieves firefox-ci credentials upon login and checks for credentials before performing any taskcluster action. If you're hitting a scope error for one particular test, it's probably because that particular test isn't configured correctly.