Missing scope to create Taskcluster task/hook

RESOLVED FIXED

Status

Taskcluster
General
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: Bastien Abadie, Assigned: dustin)

Tracking

Trunk

Details

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161209094039

Steps to reproduce:

I created a Taskcluster hook for the project Shipit Dashboard (example: https://tools.taskcluster.net/hooks/#project-shipit/services-staging-shipit_dashboard-bot); but the task cannot run as my client needs an extra scope: queue:create-task:aws-provisioner-v1/releng-task

I only have ueue:create-task:aws-provisioner-v1/tutorial


Actual results:

The task did not execute.


Expected results:

The task should execute and run shipit-bot from the provided docker image.
Rok, is it OK for this hook to use the releng-task workerType?
Flags: needinfo?(rgarbas)
:dustin: +1
Flags: needinfo?(rgarbas)
OK, I added
  https://tools.taskcluster.net/auth/roles/#hook-id:project-shipit%252fservices-staging-shipit_dashboard-bot

should be good to go!
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Assignee: nobody → dustin
(Reporter)

Comment 4

a year ago
Thanks Dustin, it works fine. 
But now i need to access Taskcluster Cache [1], so i also need this scope:

> releng-task:cache:shipit-bot-staging

I think this is the right scope given that the worker for this hook is releng-task. According to the documentation, it should otherwise be:

> docker-worker:cache:shipit-bot-staging


[1]: https://docs.taskcluster.net/reference/workers/docker-worker/caches
You need to log in before you can comment on or make changes to this bug.