Error when deploying to Flex - Timed out waiting for the flex deployment to become network provisioned

[Alexandre Ackermans]

Since yesterday 11 am PST we're getting an error when deploying our Google App Engine Flex project. We've filed 2 support requests (we were getting another error) but not getting attention. Can someone point us in the right direction?

ERROR: (gcloud.app.deploy) Error Response: [4] Timed out waiting for the flex deployment to become network provisioned.

 

FYI We're not deploying a much different build than the one we've been deploying daily for the last 12 months  - just a few minor changes. Total build & deployment time must take just slightly more than 10 mins. We increased our cloud deploy timeout (which defaults to 600) with

> gcloud config set app/cloud_build_timeout 1800

but now getting the network timeout error.

tail of our log below:

--

8f1f88b1ad73: Layer already exists
915717263bcf: Layer already exists
84ff92691f90: Layer already exists
8c468b8e19fa: Layer already exists
b056439591da: Layer already exists
6796d14e9344: Pushed
b448af193230: Pushed
109e44448f49: Pushed
latest: digest: 
sha256:e87463760a02df3027ec16081dcb1c6dedc7c9ce53447788fea32357e88c0a83 
size: 3672
DONE
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.app.deploy) Error Response: [4] Timed out waiting for the 
flex deployment to become network provisioned.

[Joshua Fox]

 

"Network layer provisioning" is a GCP- internal step whose speed you don't control. But there is an internal  timeout that is counted from the beginning of YOUR startup, and so   the extra time for "network layer provisioning" (plus another similar internal step) can exceed that time.  

But... the timeout in question is 25-minutes, so I don't know if that is relevant to you.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c9938f8f-9733-4112-b147-b4bf58e9269d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

 

JOSHUA FOX

Director, Software Architecture | Freightos

T (Israel): +972-545691165 | T (US):  +1-3123400953  

Smooth shipping.

[George (Cloud Platform Support)]

Hello Alexandre, 

It is difficult to offer support directly in this Group, as confidential, project-related information is needed to start investigating, and then progress is not always visible. You are at an advantage posting in the Public Issue Tracker, where, by the way, a similar issue is already present. This might be caused by a temporary resource scarcity in the Cloud, or by errors in your app's code. It is difficult to say, without a more in-depth investigation.