gcloud - ERROR: (gcloud.app.deploy) Permissions error fetching application

Question

I am trying to deploy node js app on google cloud but getting following error -

Step #1: ERROR: (gcloud.app.deploy) Permissions error fetching application [apps
/mytest-240512]. Please make sure you are using the correct project ID and that
you have permission to view applications on the project.

I am running following command -

gcloud builds submit . --config cloudbuild.yaml

My cloudbuild.yaml file looks like -

steps:
  #install
  - name: 'gcr.io/cloud-builders/npm'
    args: ['install']

   #deploy
  - name: 'gcr.io/cloud-builders/gcloud'
    args: ['app', 'deploy']

John Hanley · Accepted Answer · 2019-05-14 18:17:02Z

56

The default Cloud Build service account does not allow access to deploy App Engine. You need to enable the Cloud Build service account to perform actions such as deploy.

The Cloud Build service account is formatted like this:

[PROJECT_NUMBER]@cloudbuild.gserviceaccount.com

Go to the Google Cloud Console -> IAM & admin -> IAM.
Locate the service account and click the pencil icon.
Add the role "App Engine Deployer" to the service account.

Wait a couple of minutes for the service account to update globally and then try again.

answered May 14, 2019 at 18:17

John Hanley

81.8k7 gold badges115 silver badges181 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Sachin Vairagi Over a year ago

Thank you for your response John, I have to also enable - App engine API but now getting following message - Step #1: ERROR: (gcloud.app.deploy) Your deployment has succeeded, but promoting the new version to default failed. You may not have permissions to change traffic splits. Changing traffic splits requires the Owner, Editor, App Engine Admin, or App Engine Service Admin role. Please contact your project owner and use the gcloud app services set-traffic --splits <version>=1 command to redirect traffic to your newly deployed version.

Sachin Vairagi Over a year ago

working now, after adding "App Engine Admin" role to [PROJECT_NUMBER]@cloudbuild.gserviceaccount.com

John Hanley Over a year ago

I had assumed that you already had set up App Engine, which requires region selection, enabling services, etc. Now that you have an app deployed you should not need anything other than gcloud app deploy and App Engine Deployer permissions. It is OK to leave Cloud Build with App Engine Admin as that is a secure service controlled by Google.

Sachin Vairagi Over a year ago

is there any option in package.json to run command after build like heroku-postbuild

hamx0r Over a year ago

@SachinVairagi I found that the "Project Editor" plus "App Engine Deployer" permissions were sufficient to use Cloud Builder to deploy to GAE Standard Environment.

|

Arieck · Accepted Answer · 2023-07-21 09:03:53Z

8

You can also get this error if you forgot to enable billing on the project. I just had to go to the Google Cloud Console, search for App Engine and the billing setup popped up.

answered Jul 21, 2023 at 9:03

Arieck

2,0702 gold badges12 silver badges8 bronze badges

3 Comments

JesusDMedinaC Over a year ago

Same for me. Once I enabled billing the deploy worked inmediatelly.

xke Dec 23, 2024 at 1:36

Thanks, this was the fix for me. Really unclear error message from the "gcloud" CLI though. 😂

Alain. Jr Feb 26 at 11:34

Nice catch. It was strange to me because deployments were successful a while back. Turns out after the free trial window google cloud initially gives is expired, you need to explicitly activate Billings.

rafaelbiten · Accepted Answer · 2020-06-08 19:33:43Z

6

I had this same error today and the way I resolve it was by running: $ gcloud auth login on the console.

This will open a new browser tab for you to login with the credentials that has access to the project you're trying to deploy.

I was able to deploy to gcloud after that.

ps.: I'm not sure this is the best approach, but I'm leaving this as a possible solution as this is how I usually go around this problem. Worst case, I'll stand corrected and learn something new.

answered Jun 8, 2020 at 19:33

rafaelbiten

6,2822 gold badges38 silver badges38 bronze badges

Comments

DazWilkin · Accepted Answer · 2019-05-14 17:32:02Z

5

The most common way to deploy an app to App Engine is to use gcloud app deploy ....

When you use gcloud app deploy against App Engine Flex, the service uses Cloud Build.

It's entirely possible|reasonable to use Cloud Build to do your deployments too, it's just more involved.

I've not tried this but I think that, if you wish to use Cloud Build to perform the deployment, you will need to ensure that the Cloud Build service account has permissions to deploy to App Engine.

Here's an example of what you would need to do, specifically granting Cloud Build's service account the correct role.

answered May 14, 2019 at 17:32

DazWilkin

41.7k8 gold badges61 silver badges113 bronze badges

Comments

Eric Lannert · Accepted Answer · 2020-05-01 22:29:32Z

2

Two commands can handle the perms needed (run in your terminal if you have gcloud sdk installed and authenticated or run in cloud shell for your project):

export PROJECT_ID=[[put your project id here]]
export PROJECT_NUMBER=$(gcloud projects describe $PROJECT_ID --format="value(projectNumber)")

gcloud iam service-accounts add-iam-policy-binding ${PROJECT_ID}@appspot.gserviceaccount.com \
--member=serviceAccount:${PROJECT_NUMBER}@cloudbuild.gserviceaccount.com \
--role=roles/iam.serviceAccountUser \
--project=${PROJECT_ID}
```
gcloud projects add-iam-policy-binding ${PROJECT_ID} \
--member=serviceAccount:${PROJECT_NUMBER}@cloudbuild.gserviceaccount.com \
--role=roles/appengine.appAdmin

answered May 1, 2020 at 22:29

Eric Lannert

233 bronze badges

1 Comment

James Joyce Over a year ago

Thanks - worked well - just needed to remove the ``` to allow the full command to execute!

starball · Accepted Answer · 2023-07-20 21:05:22Z

1

In my case, the issue was that I have mistaken project ID for project NAME

edited Jul 20, 2023 at 21:05

starball♦

59.6k53 gold badges315 silver badges1k bronze badges

answered Jul 20, 2023 at 14:54

Bugs Bunny

2,6841 gold badge28 silver badges35 bronze badges

Comments

Jaideep · Accepted Answer · 2024-08-02 19:09:52Z

1

Even though it shows error like below saying "permissions error"

ERROR: (gcloud.app.deploy) Permissions error fetching application [apps/my-react-blog-dummy]. Please make sure that you have permission to view applications on the project and that [email protected] has the App Engine Deployer (roles/appengine.deployer) role.

Just after adding billing details, it worked using this link https://console.cloud.google.com/billing

edited Aug 2, 2024 at 19:09

answered Aug 2, 2024 at 15:02

Jaideep

1,0289 silver badges22 bronze badges

1 Comment

Alvaro Rodriguez Scelza Over a year ago

Thanks, indeed such a misleading error. In my case I was asked to create the billing account for the project but it didn't automatically assign it after created.

Collectives™ on Stack Overflow

gcloud - ERROR: (gcloud.app.deploy) Permissions error fetching application

7 Answers 7

7 Comments

3 Comments

Comments

Comments

1 Comment

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

7 Comments

3 Comments

Comments

Comments

1 Comment

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related