The principal (user or service account) lacks IAM permission “cloudtasks.tasks.create” for the resource
The above error message is being thrown when I try to add a task to a queue. Here is my setup and the info about this problem:
- Project ID:
my-project - Service Account ID:
my-service-account
- Task Queue Name:
my-queue
- Task Queue Location:
asia-northeast1(one of the few locations where Cloud Task is currently in beta)
Also, let's confirm that all the above exist and are running.
When I check my service account roles by POSTING to https://cloudresourcemanager.googleapis.com/v1/projects/my-project:getIamPolicy
I receive a response similar to:
{
"status": 200,
"data":
{
"version": 1,
"etag": "BwV6nNWJg4E=",
"bindings": [
{
"role": "roles/cloudtasks.admin",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
},
{
"role": "roles/cloudtasks.enqueuer",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
}]
}
}
As you can see, my-service-account has the following 2 roles:
- roles/cloudtasks.admin
- roles/cloudtasks.enqueuer
Both of those roles have the cloudtasks.tasks.create permission baked in.
When I try to add a task to the Cloud Task using the following:
POST https://cloudtasks.googleapis.com/v2beta3/projects/my-project/locations/asia-northeast1/queues/my-queue/tasks + task payload
I receive the following error message:
{
"status": 403,
"data":
{
"error":
{
"code": 403,
"message": "The principal (user or service account) lacks IAM permission "cloudtasks.tasks.create" for the resource "projects/my-project/locations/asia-northeast1/queues/my-queue" (or the resource may not exist).",
"status": "PERMISSION_DENIED"
}
}
}
This really puzzles me.
Is there anybody who knows what I might be doing wrong?
google-api google-cloud-platform google-iam
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
add a comment |
The above error message is being thrown when I try to add a task to a queue. Here is my setup and the info about this problem:
- Project ID:
my-project - Service Account ID:
my-service-account
- Task Queue Name:
my-queue
- Task Queue Location:
asia-northeast1(one of the few locations where Cloud Task is currently in beta)
Also, let's confirm that all the above exist and are running.
When I check my service account roles by POSTING to https://cloudresourcemanager.googleapis.com/v1/projects/my-project:getIamPolicy
I receive a response similar to:
{
"status": 200,
"data":
{
"version": 1,
"etag": "BwV6nNWJg4E=",
"bindings": [
{
"role": "roles/cloudtasks.admin",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
},
{
"role": "roles/cloudtasks.enqueuer",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
}]
}
}
As you can see, my-service-account has the following 2 roles:
- roles/cloudtasks.admin
- roles/cloudtasks.enqueuer
Both of those roles have the cloudtasks.tasks.create permission baked in.
When I try to add a task to the Cloud Task using the following:
POST https://cloudtasks.googleapis.com/v2beta3/projects/my-project/locations/asia-northeast1/queues/my-queue/tasks + task payload
I receive the following error message:
{
"status": 403,
"data":
{
"error":
{
"code": 403,
"message": "The principal (user or service account) lacks IAM permission "cloudtasks.tasks.create" for the resource "projects/my-project/locations/asia-northeast1/queues/my-queue" (or the resource may not exist).",
"status": "PERMISSION_DENIED"
}
}
}
This really puzzles me.
Is there anybody who knows what I might be doing wrong?
google-api google-cloud-platform google-iam
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
I'm getting the same issue out of nowhere. My creds were working great, and with no code changes, this error started popping up. No solution on my side.
– Kyle Hotchkiss
Dec 19 '18 at 18:05
To fix this I had to blow up all the roles and then re-add them. The only thing that comes to my mind is that I change the roles on the console, and then I also used the API. I feel that updating the roles mixing the API and the console might have created that bug.
– Nicolas Dao
Dec 24 '18 at 5:26
add a comment |
The above error message is being thrown when I try to add a task to a queue. Here is my setup and the info about this problem:
- Project ID:
my-project - Service Account ID:
my-service-account
- Task Queue Name:
my-queue
- Task Queue Location:
asia-northeast1(one of the few locations where Cloud Task is currently in beta)
Also, let's confirm that all the above exist and are running.
When I check my service account roles by POSTING to https://cloudresourcemanager.googleapis.com/v1/projects/my-project:getIamPolicy
I receive a response similar to:
{
"status": 200,
"data":
{
"version": 1,
"etag": "BwV6nNWJg4E=",
"bindings": [
{
"role": "roles/cloudtasks.admin",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
},
{
"role": "roles/cloudtasks.enqueuer",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
}]
}
}
As you can see, my-service-account has the following 2 roles:
- roles/cloudtasks.admin
- roles/cloudtasks.enqueuer
Both of those roles have the cloudtasks.tasks.create permission baked in.
When I try to add a task to the Cloud Task using the following:
POST https://cloudtasks.googleapis.com/v2beta3/projects/my-project/locations/asia-northeast1/queues/my-queue/tasks + task payload
I receive the following error message:
{
"status": 403,
"data":
{
"error":
{
"code": 403,
"message": "The principal (user or service account) lacks IAM permission "cloudtasks.tasks.create" for the resource "projects/my-project/locations/asia-northeast1/queues/my-queue" (or the resource may not exist).",
"status": "PERMISSION_DENIED"
}
}
}
This really puzzles me.
Is there anybody who knows what I might be doing wrong?
google-api google-cloud-platform google-iam
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
The above error message is being thrown when I try to add a task to a queue. Here is my setup and the info about this problem:
- Project ID:
my-project - Service Account ID:
my-service-account
- Task Queue Name:
my-queue
- Task Queue Location:
asia-northeast1(one of the few locations where Cloud Task is currently in beta)
Also, let's confirm that all the above exist and are running.
When I check my service account roles by POSTING to https://cloudresourcemanager.googleapis.com/v1/projects/my-project:getIamPolicy
I receive a response similar to:
{
"status": 200,
"data":
{
"version": 1,
"etag": "BwV6nNWJg4E=",
"bindings": [
{
"role": "roles/cloudtasks.admin",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
},
{
"role": "roles/cloudtasks.enqueuer",
"members": [
"serviceAccount:my-service-account@my-project.iam.gserviceaccount.com"
]
}]
}
}
As you can see, my-service-account has the following 2 roles:
- roles/cloudtasks.admin
- roles/cloudtasks.enqueuer
Both of those roles have the cloudtasks.tasks.create permission baked in.
When I try to add a task to the Cloud Task using the following:
POST https://cloudtasks.googleapis.com/v2beta3/projects/my-project/locations/asia-northeast1/queues/my-queue/tasks + task payload
I receive the following error message:
{
"status": 403,
"data":
{
"error":
{
"code": 403,
"message": "The principal (user or service account) lacks IAM permission "cloudtasks.tasks.create" for the resource "projects/my-project/locations/asia-northeast1/queues/my-queue" (or the resource may not exist).",
"status": "PERMISSION_DENIED"
}
}
}
This really puzzles me.
Is there anybody who knows what I might be doing wrong?
google-api google-cloud-platform google-iam
google-api google-cloud-platform google-iam
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
edited Nov 15 '18 at 8:22
Nicolas Dao
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
asked Nov 14 '18 at 22:40
Nicolas DaoNicolas Dao
258211
258211
I'm getting the same issue out of nowhere. My creds were working great, and with no code changes, this error started popping up. No solution on my side.
– Kyle Hotchkiss
Dec 19 '18 at 18:05
To fix this I had to blow up all the roles and then re-add them. The only thing that comes to my mind is that I change the roles on the console, and then I also used the API. I feel that updating the roles mixing the API and the console might have created that bug.
– Nicolas Dao
Dec 24 '18 at 5:26
add a comment |
I'm getting the same issue out of nowhere. My creds were working great, and with no code changes, this error started popping up. No solution on my side.
– Kyle Hotchkiss
Dec 19 '18 at 18:05
To fix this I had to blow up all the roles and then re-add them. The only thing that comes to my mind is that I change the roles on the console, and then I also used the API. I feel that updating the roles mixing the API and the console might have created that bug.
– Nicolas Dao
Dec 24 '18 at 5:26
I'm getting the same issue out of nowhere. My creds were working great, and with no code changes, this error started popping up. No solution on my side.
– Kyle Hotchkiss
Dec 19 '18 at 18:05
I'm getting the same issue out of nowhere. My creds were working great, and with no code changes, this error started popping up. No solution on my side.
– Kyle Hotchkiss
Dec 19 '18 at 18:05
To fix this I had to blow up all the roles and then re-add them. The only thing that comes to my mind is that I change the roles on the console, and then I also used the API. I feel that updating the roles mixing the API and the console might have created that bug.
– Nicolas Dao
Dec 24 '18 at 5:26
To fix this I had to blow up all the roles and then re-add them. The only thing that comes to my mind is that I change the roles on the console, and then I also used the API. I feel that updating the roles mixing the API and the console might have created that bug.
– Nicolas Dao
Dec 24 '18 at 5:26
add a comment |
1 Answer
1
active
oldest
votes
I have no clues why that worked, but I blew out all the roles and then added them again and then it worked. Seems to be a bug on Google Cloud Platform.
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309804%2fthe-principal-user-or-service-account-lacks-iam-permission-cloudtasks-tasks-c%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have no clues why that worked, but I blew out all the roles and then added them again and then it worked. Seems to be a bug on Google Cloud Platform.
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
add a comment |
I have no clues why that worked, but I blew out all the roles and then added them again and then it worked. Seems to be a bug on Google Cloud Platform.
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
add a comment |
I have no clues why that worked, but I blew out all the roles and then added them again and then it worked. Seems to be a bug on Google Cloud Platform.
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
I have no clues why that worked, but I blew out all the roles and then added them again and then it worked. Seems to be a bug on Google Cloud Platform.
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
answered Nov 15 '18 at 8:31
Nicolas DaoNicolas Dao
258211
258211
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309804%2fthe-principal-user-or-service-account-lacks-iam-permission-cloudtasks-tasks-c%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'm getting the same issue out of nowhere. My creds were working great, and with no code changes, this error started popping up. No solution on my side.
– Kyle Hotchkiss
Dec 19 '18 at 18:05
To fix this I had to blow up all the roles and then re-add them. The only thing that comes to my mind is that I change the roles on the console, and then I also used the API. I feel that updating the roles mixing the API and the console might have created that bug.
– Nicolas Dao
Dec 24 '18 at 5:26