Appengine deployment error

[Jagath Weerasinghe]

Hi All, 

We have been running appengine deployment smoothly till yesterday. Yesterday gcloud deploy started to complain about cloudscheduler.googleapis.com. I enabled the cloudscheduler APIs and retried the deployment. Then that error message disappeared but still, deployment fails with the following error. 

Updating config [cron]...failed.                                                                                                                                                                   

DEBUG: 'NoneType' object is not subscriptable

We are using the latest cloud SDK version. 

gcloud version:

Google Cloud SDK 325.0.0

alpha 2021.01.22

app-engine-java 1.9.84

app-engine-python 1.9.91

beta 2021.01.22

bq 2.0.64

core 2021.01.22

gsutil 4.58

I would like to know whether any of you experienced the same issue. Any advice would be greatly appreciated. 

Thanks,

Jagath

[Elliott (Cloud Platform Support)]

Hello

Thank you for your question. I know it is frustrating when an app cannot deploy. There was an issue yesterday for some App Engine Flexible deployments that failed with a timeout. That issue with Google App Engine was resolved for all affected projects as of Tuesday. I hope this did not cause inconvenience to you.

We appreciate your patience while we worked on resolving the issue.

If you have other related questions, please let us know.

[Jagath Weerasinghe]

Hello, 

Thanks for the reply. We have several projects in us-central1 and europe-west1 regions. All the projects experience the same issue. 

We are running appengine standard version and we did not experience a time-out issue recently. 

Do you have more information about the issue. For example, whether the issue is related only to the cron job deployment, if so, and if we skip cron job deployment would the deployment still work? Or is there any other workaround?

Thank you, 

Jagath

[Jagath Weerasinghe]

Hello, 

Looks like deploying cron (no changes to cron jobs from our last deployment) is the issue. I skipped cron and the deployment worked. 

I had to enable cloudtasks.googleapis.com for deploying task queues. 

Jagath

[Elliott (Cloud Platform Support)]

Hello Jagath,

I’m glad that you were able to find the root cause of the deployment error and now you are able to deploy. You were correct to enable the API since you apparently needed it in your case.

I was able to provide you with the publicly available information regarding the common issue reported on Tuesday and I hope it is no longer causing you difficulties.

If you have similar issues in the future and wish to have a general discussion regarding that, you may create another Google Groups thread.

Thank you for your patience and I wish you success in your application.

[Jagath Weerasinghe]

Hello Elliot, 

I guess the relevant engineering teams are aware of this issue, as we can not keep skipping the cron job deployment like this. 

Thanks, 

Jagath

[Elliott (Cloud Platform Support)]

Hello Jagath,

The issue that I was referring to was related to deployment of applications in general and it was resolved yesterday. It appears that your question and scenario may be unrelated and needs to be investigated further. What is the actual error you are getting? Please provide a redacted version and we will look into this for you. I was under the impression that there was a configuration issue in your project and once you corrected it, you were able to deploy without a problem. It appears that I was mistaken and if this is the case, please tell. Google Groups is meant for general discussions but if you want to report a common issue, you may use Google Issue Tracker.

I will wait for your response and apologies if I misunderstood.

[Alan deLespinasse]

I'm having the same issue. This was working fine until a couple days ago. The last known successful deploy was January 25 at 17:43 EST. The first known failure was January 26 at 13:44 EST. Example transcript:

> gcloud app --quiet --project gamalon-emailabz-debug deploy cron.yaml

Configurations to update:

descriptor:      [/home/aldel/emailabz/server/cron.yaml]

type:            [cron jobs]

target project:  [gamalon-emailabz-debug]

Updating config [cron]...failed.                                                                                                                                                                                    

ERROR: gcloud crashed (TypeError): 'NoneType' object is not subscriptable

If you would like to report this issue, please run the following command:

  gcloud feedback

To check gcloud for common problems, please run the following command:

  gcloud info --run-diagnostics

The cron.yaml is very simple and has not changed.

[Alan deLespinasse]

I think it's this bug: https://issuetracker.google.com/issues/178529949

[Alan deLespinasse]

And indeed setting a job_age_limit on the cron job seems to avoid the error for me. Still seems like a bug was introduced somewhere.

[Jagath Weerasinghe]

I commented on the issue tracker. The documentation says the retry_parameters are optional, so it should be a bug. 

[Jose V]

Hello,

Indeed, it looks like some issues were introduced with Cloud SDK version 325.0.0 to the App Engine cron.yaml deployment process. Here is another Issue Tracker entry about a similar issue: https://issuetracker.google.com/178780288

The engineering team is aware of this. I suggest you follow the Issue Tracker entries mentioned in this thread for further updates on the matter

Regards

[Jagath Weerasinghe]

Thank you! Waiting for the fix. 

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6bb3ffcd-735e-4d96-804d-9d2745f4db9fn%40googlegroups.com.

[Jagath Weerasinghe]

Tried SDK 326.0.0. Cron deployment worked smoothly for me.  Thanks all!