Permanent error after switching to invalid runtime

[mark4]

I mistakenly changed my runtime from python37 to python312.
When I then did `gcloud --project=diffpdf app deploy app.yaml` it uploaded
all my files but failed due to a 'NoSuchKey' error.

I then changed my runtime back to python37 but it now gives the same error.
I also tried python39 and python310.

So clearly my original mistake has led to a permanent change to my GAE
project which means I can't return to any valid runtime.

How can I restore my project so that it uses a valid runtime?

[christianpaula]

Hi @mark4,

Welcome to Google Cloud Community!

To restore your GAE project so that it uses a valid runtime, you can either delete and re-deploy your project or update your project's runtime configuration. If you still have problems, you can contact Google Cloud support for assistance.

Note: If you are using a custom runtime, you will need to make sure that it is compatible with the version of GAE that you are using. You can check the runtime compatibility list: App Engine standard environment runtimes for more information.

[mark4]

Hi @christianpaula ,

I'm using a standard runtime. I tried updating the runtime configuration in app.yaml but as I already mentioned that didn't help.

I'm also wondering if ndb has changed since I use that and I've been told that a change to that could prevent a successful deployment. If this is a concurrent problem then deleting and re-deploying won't fix it.

I can't get help from google support because when I clicked "buy now" it just took me to a page which said I had to change my GAE configuration and when I looked into that it was asking me to do lots of changes most of which I didn't understand and anyway didn't want.

[mark4 · Accepted solution]

In the end it turned out the problem wasn't the change of runtime or anything to do with ndb. It was some GAE cache-related bug. This was solved by using the gcloud --no-cache option.