Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

App Engine Standard Java 17 deployment issue

Hello Google Cloud Community,

My problem is that I can't deploy any more several App Engine Standard Java 17 web applications that several months ago deployed without issue.
And for 2 of them, I didn't change any file in the source code and config, but none of them simply doesn't deploy any more.
The only thing I did several months ago was, after a successful deployment, delete all Cloud Storage buckets generated by Cloud Build.

Here is the mvn appengine:deploy error I get:

ERROR: (gcloud.app.deploy) Error Response: [9] Cloud build 24b09194-7895-433a-9c68-6cae4630b587 status: FAILURE
[INFO] GCLOUD: An unexpected error occurred. Refer to build logs: ...

And here is the build log:

Starting Step #2 - "build"
Step #2 - "build": Already have image (with digest): eu.gcr.io/gae-runtimes/buildpacks/google-gae-22/java/builder:java_20231030_RC00
Step #2 - "build": ===> ANALYZING
Step #2 - "build": ERROR: failed to initialize analyzer: getting previous image: getting config file for image "eu.gcr.io/PROJECTID/app-engine-tmp/app/default/ttl-18h:latest": GET https://storage.googleapis.com/eu.artifacts.PROJECTID.appspot.com/containers/images/sha256:036aff03a...: unexpected status code 404 Not Found: <?xml version='1.0' encoding='UTF-8'?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Details>No such object: eu.artifacts.PROJECTID.appspot.com/containers/images/sha256:036aff03ac31731663e8aee494f16b733e1c56e31b329b9db470007802a361e7</Details></Error>
Finished Step #2 - "build"
ERROR
ERROR: build step 2 "eu.gcr.io/gae-runtimes/buildpacks/google-gae-22/java/builder:java_20231030_RC00" failed: step exited with non-zero status: 1

Indeed, the referenced file does not exist. But why does Cloud Build try to access it if it did not upload it first into Cloud Storage?

I also tried to repair the project with gcloud beta app repair --project PROJECTID but it doesn't fix the problem.

What steps can I do to address my problem? Is there a bug in Cloud Build?

And can you confirm that Cloud Storage buckets can be (manually or through an API) deleted after a successful Cloud Build?

Thank you very much in advance for your help,

Cyril B.

0 2 2,093
2 REPLIES 2

Hi @Cyril_B,

Based on this documentation on using the default bucket for App Engine:

When you create an app, App Engine creates a default bucket that provides the first 5GB of storage for free. The default bucket also includes a free quota for Cloud Storage I/O operations.

App Engine also creates a bucket that it uses for temporary storage when it deploys new versions of your app. This bucket is for use by App Engine only. Apps can't interact with this bucket.


This would contain other files necessary to run your app.

I would suggest checking your app.yaml if the runtime is correct or updated (Java 8 or 11 or 17), check if your gcloud CLI is updated to its current version and if Maven plugin is added to your pom.xml file. You can follow the steps through this link.

If the aforementioned steps didn't work, you may either reach out to our support hub or file this one as a bug through this issue tracker link. For filing issues, we don't have a specific ETA but you can keep track of its progress once the ticket has been created.

Hope this helps.

Thank you @robertcarlos

By browsing through the bugtracker issues, I found something useful: to solve the issue, I needed to migrate manually each affected project from Container Registry to Artifact Registry.

See https://cloud.google.com/artifact-registry/docs/transition/setup-gcr-repo#redirect-enable