CODEWITHSUNDEEP
google-app-enginedeploymentrestore
user1089109
user1089109

Reputation: 13

Deployment to GAE failing after project has been restored

I had a project deployment to GAE using cloud build which was working fine, But I deleted the project by mistake. But after the restore, the deployment is failing with

ERROR: (gcloud.app.deploy) Error Response: [4] Timed out waiting for the app infrastructure to become healthy.

I see this in the cloud build logs: even when the Cloud build service account has the App Engine Admin Permissions

WARNING: Unable to verify that the Appengine Flexible API is enabled for project []. You may not have permission to list enabled services on this project. If it is not enabled, this may cause problems in running your deployment. Please ask the project owner to ensure that the Appengine Flexible API has been enabled and that this account has permission to list enabled APIs.

Also, the permissions for the account owner has changed from : 1350/1578 to 1266/1578. How can I fix that?

Upvotes: 1

Views: 812

Answers (1)

Deniss T.
Deniss T.

Reputation: 2652

I have tried to replicate the issue you're experiencing by creating a new project and deploying a simple HelloWorld app in GAE Flexible environment.

I have deleted my project and then restored it, and, after that, I was unable to deploy the app again. The issue was solved once I made sure my Google App Engine Flexible Environment API is enabled and linked my Billing Account again (as it gets removed when you delete the project).

EDIT:

After further research, I found this page in the GCP issue tracker.

Based on the information from that page, the error you are experiencing can occur for various reasons. It can be related to quotas (e.g. CPU cores, memory, public IP addresses) or, sometimes, the region where you are trying to deploy.

As it was confirmed by the engineer, trying to re-deploy, or to deploy in a different region often resolves the issue. However, if the issue persists and you have a support package, I'd recommend you to contact GCP support as the issue is too broad to troubleshoot it here and may require a project inspection.

Upvotes: 1

Related Questions