gcloud app deploy fails - Error Response: [4] Timeout

[Dean van Niekerk]

Im trying to deploy the hello world nodejs app, the build is successful but it then fails on deployment??

Any ideas? I have tried multiple times in the last 24rhs and still get the same issue.

DEPLOYMENT ERROR

===================

Updating service [default] (this may take several minutes)...failed.

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

BUILD LOG

=========

starting build "d8d6e9c7-7022-4ffe-87ba-4e784c5bcd9e"

FETCHSOURCE

Fetching storage object: gs://staging.coinkraal.appspot.com/eu.gcr.io/coinkraal/appengine/default.20180309t105858:latest#1520585954395074

Copying gs://staging.coinkraal.appspot.com/eu.gcr.io/coinkraal/appengine/default.20180309t105858:latest#1520585954395074...

/ [0 files][ 0.0 B/ 46.9 KiB] 

/ [1 files][ 46.9 KiB/ 46.9 KiB] 

Operation completed over 1 objects/46.9 KiB. 

BUILD

Starting Step #0

Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:e815f1f724fd21fb11ff1ea1eee0c535f5524905255b5cede9d780dc98210f1d

Step #0: sha256:e815f1f724fd21fb11ff1ea1eee0c535f5524905255b5cede9d780dc98210f1d: Pulling from gcp-runtimes/nodejs/gen-dockerfile

Step #0: Digest: sha256:e815f1f724fd21fb11ff1ea1eee0c535f5524905255b5cede9d780dc98210f1d

Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:e815f1f724fd21fb11ff1ea1eee0c535f5524905255b5cede9d780dc98210f1d

Step #0: Checking for Node.js.

Finished Step #0

Starting Step #1

Step #1: Pulling image: gcr.io/cloud_builders/docker@sha256:b4cc2024cfe3fde8bfb17701b1bea4d038e6dfd48423abdb28e3be3545e55ce0

Step #1: sha256:b4cc2024cfe3fde8bfb17701b1bea4d038e6dfd48423abdb28e3be3545e55ce0: Pulling from cloud_builders/docker

Step #1: cf2c5e27174e: Already exists

Step #1: a7bc5eb395b5: Already exists

Step #1: a19c45128315: Already exists

Step #1: d7d685446745: Pulling fs layer

Step #1: d7d685446745: Verifying Checksum

Step #1: d7d685446745: Download complete

Step #1: d7d685446745: Pull complete

Step #1: Digest: sha256:b4cc2024cfe3fde8bfb17701b1bea4d038e6dfd48423abdb28e3be3545e55ce0

Step #1: Status: Downloaded newer image for gcr.io/cloud_builders/docker@sha256:b4cc2024cfe3fde8bfb17701b1bea4d038e6dfd48423abdb28e3be3545e55ce0

Step #1: Sending build context to Docker daemon 239.1kB

Step #1: Step 1/5 : FROM gcr.io/google-appengine/nodejs@sha256:55a813c7ae297b6dea54f1a039be415d4f0c4a7bba6445186ceb6b0ac983a319

Step #1: sha256:55a813c7ae297b6dea54f1a039be415d4f0c4a7bba6445186ceb6b0ac983a319: Pulling from google-appengine/nodejs

Step #1: Digest: sha256:55a813c7ae297b6dea54f1a039be415d4f0c4a7bba6445186ceb6b0ac983a319

Step #1: Status: Downloaded newer image for gcr.io/google-appengine/nodejs@sha256:55a813c7ae297b6dea54f1a039be415d4f0c4a7bba6445186ceb6b0ac983a319

Step #1: ---> f8013bcfc8b6

Step #1: Step 2/5 : COPY . /app/

Step #1: ---> cb74cd6cc6b2

Step #1: Step 3/5 : RUN /usr/local/bin/install_node '>=4.3.2'

Step #1: ---> Running in 6145b499d252

Step #1: Removing intermediate container 6145b499d252

Step #1: ---> 8af305b2220c

Step #1: Step 4/5 : RUN npm install --unsafe-perm || ((if [ -f npm-debug.log ]; then cat npm-debug.log; fi) && false)

Step #1: ---> Running in 34696094a5ea

Step #1: added 49 packages in 2.53s

Step #1: Removing intermediate container 34696094a5ea

Step #1: ---> 3f488f978a43

Step #1: Step 5/5 : CMD npm start

Step #1: ---> Running in d0182921264b

Step #1: Removing intermediate container d0182921264b

Step #1: ---> 9ed4a1923b74

Step #1: Successfully built 9ed4a1923b74

Step #1: Successfully tagged eu.gcr.io/coinkraal/appengine/default.20180309t105858:latest

Finished Step #1

PUSH

Pushing eu.gcr.io/coinkraal/appengine/default.20180309t105858:latest

The push refers to repository [eu.gcr.io/coinkraal/appengine/default.20180309t105858]

3fc0c9ef7239: Preparing

2d061162458c: Preparing

bc37093ecf8a: Preparing

b0532b80ed9e: Preparing

87c9a22fb286: Preparing

34b3438ad618: Preparing

de5e96f3b52d: Preparing

647127451460: Preparing

0529bceacd9f: Preparing

21df82f90a72: Preparing

34b3438ad618: Waiting

de5e96f3b52d: Waiting

647127451460: Waiting

0529bceacd9f: Waiting

21df82f90a72: Waiting

87c9a22fb286: Layer already exists

b0532b80ed9e: Layer already exists

bc37093ecf8a: Layer already exists

de5e96f3b52d: Layer already exists

647127451460: Layer already exists

34b3438ad618: Layer already exists

21df82f90a72: Layer already exists

0529bceacd9f: Layer already exists

2d061162458c: Pushed

3fc0c9ef7239: Pushed

latest: digest: sha256:738f120746e8af2cfed736ac799f6cb76bf467973a701da434ae98076b9a5236 size: 2415

DONE

[George (Cloud Platform Support)]

To follow-up easily and be notified of all developments towards the solving of the issue, it is recommendable to open another similar issue in the public issue tracker. In fact, this error is already known as "Google App Engine Flexible: Error Response: [4] Timed out waiting for the app infrastructure to become healthy."