gcloud app engine flexible deployments fail because of timeout

[Tristan]

Hi,

Since sept 26th, it's very difficult (or impossible) to deploy modules.

We face the following error:

"ERROR: (gcloud.app.deploy) Error Response: [13] Timed out when starting VMs.  It's possible that the application code is unhealthy.  (0/1 ready, 1 still deploying)."

But my instance is healthy (log contains: "vm_runtime_init: Done start 'ah_start'.").

It looks like the deployment became slower for a week but a timeout (on gcloud side?) remained unchanged and too low.

Some modules require 3 to 4 attempts to succeed and some (a bit heavier) always fail.

Is there a way to raise this timeout or any other workaround?

Deploy command:

gcloud add deploy --stop-previous-version --promote --image-url=/path/to/my/docker/image my.yaml

gcloud is up to date

We use custom runtimes based on gcr.io/google_appengine/python

bests,

[Zachary Newman]

Thanks for reporting, Tristan. I'll forward this to the appropriate folks internally.

--
You received this message because you are subscribed to the Google Groups "Google Cloud Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-dev/1500b115-cf2a-4e0c-9377-2c8f795b450f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Zachary Newman]

Is your application running on Managed VMs (vm: true) or Flexible Environment (env: flex)? If it was the latter, the default start-up time was accidentally shortened. It should have been fixed at around 5:30PM PST last night–are you still seeing this issue today?

[Tristan Croiset]

Hi Zachary,

We use "vm: true" and the issue continues today.

Le mar. 4 oct. 2016 à 17:00, Zachary Newman <z...@google.com> a écrit :

Is your application running on Managed VMs (vm: true) or Flexible Environment (env: flex)? If it was the latter, the default start-up time was accidentally shortened. It should have been fixed at around 5:30PM PST last night–are you still seeing this issue today?

On Tue, Oct 4, 2016 at 10:33 AM, Zachary Newman <z...@google.com> wrote:

Thanks for reporting, Tristan. I'll forward this to the appropriate folks internally.

On Tue, Oct 4, 2016 at 10:13 AM, Tristan <tri...@karos.fr> wrote:

Hi,

Since sept 26th, it's very difficult (or impossible) to deploy modules.

We face the following error:

"ERROR: (gcloud.app.deploy) Error Response: [13] Timed out when starting VMs.  It's possible that the application code is unhealthy.  (0/1 ready, 1 still deploying)."

But my instance is healthy (log contains: "vm_runtime_init: Done start 'ah_start'.").

It looks like the deployment became slower for a week but a timeout (on gcloud side?) remained unchanged and too low.

Some modules require 3 to 4 attempts to succeed and some (a bit heavier) always fail.

Is there a way to raise this timeout or any other workaround?

Deploy command:

gcloud add deploy --stop-previous-version --promote --image-url=/path/to/my/docker/image my.yaml

gcloud is up to date

We use custom runtimes based on gcr.io/google_appengine/python

bests,

--
You received this message because you are subscribed to the Google Groups "Google Cloud Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-d...@googlegroups.com.

[Zachary Newman]

Hi Tristan,

Please reply to me (not the group! moving to BCC) with as much of the following data as possible:

- Project ID

- App service and versions that you've seen exhibit this behavior (even if it's all of them, give me a few specific ones)

- app.yaml, and a description of your app (e.g. what the startup process is like)

- Any other project details that might be relevant.

I'll send it over to the appropriate team to investigate.

Cheers,

Zack

On Tue, Oct 4, 2016 at 11:02 AM, Tristan Croiset <tri...@karos.fr> wrote:

Hi Zachary,

We use "vm: true" and the issue continues today.

Le mar. 4 oct. 2016 à 17:00, Zachary Newman <z...@google.com> a écrit :

Is your application running on Managed VMs (vm: true) or Flexible Environment (env: flex)? If it was the latter, the default start-up time was accidentally shortened. It should have been fixed at around 5:30PM PST last night–are you still seeing this issue today?

On Tue, Oct 4, 2016 at 10:33 AM, Zachary Newman <z...@google.com> wrote:

Thanks for reporting, Tristan. I'll forward this to the appropriate folks internally.

On Tue, Oct 4, 2016 at 10:13 AM, Tristan <tri...@karos.fr> wrote:

Hi,

Since sept 26th, it's very difficult (or impossible) to deploy modules.

We face the following error:

"ERROR: (gcloud.app.deploy) Error Response: [13] Timed out when starting VMs.  It's possible that the application code is unhealthy.  (0/1 ready, 1 still deploying)."

But my instance is healthy (log contains: "vm_runtime_init: Done start 'ah_start'.").

It looks like the deployment became slower for a week but a timeout (on gcloud side?) remained unchanged and too low.

Some modules require 3 to 4 attempts to succeed and some (a bit heavier) always fail.

Is there a way to raise this timeout or any other workaround?

Deploy command:

gcloud add deploy --stop-previous-version --promote --image-url=/path/to/my/docker/image my.yaml

gcloud is up to date

We use custom runtimes based on gcr.io/google_appengine/python

bests,

--
You received this message because you are subscribed to the Google Groups "Google Cloud Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-dev/1500b115-cf2a-4e0c-9377-2c8f795b450f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Cloud Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-dev/CALWR7Pk-RQ44kEpfj_cLqZ%2BKrMFr77DjKw6%3DqCFubwvBSw1XFg%40mail.gmail.com.