App Engine Flexible: Timed out waiting for the app infrastructure to become healthy
Asked Answered
A

3

9

I'm trying several times to deploy a new version of a service on my app engine flexible instance using the sdk and the command gcloud app deploy, but all i get is this error

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

.

I Couldn't found any answer about it on the issue tracker of gcp.

On this question, he got the same problem, but no one could answered it.

Any guidance will be very helpfull.

Apperceive answered 1/2, 2018 at 15:28 Comment(1)
Check your app log for any signs that your app isn't actually healthy. Check that your app properly responds to health checks. Maybe adjust the health checks config in your app.yaml if your app takes an unusually long time to start or, better yet, shorted that start time.Spandau
A
6

According to the gcp team, this particular error was caused because we reached the "In-use IP addresses" quota limit.

They also said that are working on improve the error messages.

"The engineering team has just created a fix for better quota error details. There is no ETA for when the fix will be released, but I would guess it would be in the next version of gcloud."

Apperceive answered 22/2, 2018 at 19:24 Comment(1)
I had exactly the same issue and it took some time to figure out. You can check if this is your issue by going to the "Activity" tab of your project home page. You may have warnings about quota limits and VMs failing to be created. App Engine deployments by default leave previous versions up and running, which might be taking up IP addresses. You can delete previous deployments, and/or request an increase in your IP address quota limit. I requested the limit to be doubled and it was approved within the day.Jevon
E
3

Over half a year later after Loneck's answer I've got the same error. I guessed it could be anything. This is why I've choosen to delete the project, create a new one in a new zone and deployed it there. Then it worked for me. It might have been any other limitation in the zone that I've choosen at the beginning.

Endocardium answered 31/10, 2018 at 18:40 Comment(0)
D
1

I ran into this and solved it by retrying the deploy 3 times.

Dorothadorothea answered 3/6, 2020 at 20:14 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.