Java app deployment fails with Invalid Semantic Version

[ABartoszek]

[OUTDATED] 
Problem has been resolved without any intervention from our side probably with some inside GCP bugfix.

Hello Google Cloud Community,

I’ve encountered an issue deploying my application to Standard App Engine using runtime: java21 with ubuntu2204. 
This deployment setup has worked perfectly in the past.


(error log)
Step #2 - "build": failed to build: (error ID: 3d9223eb):
Step #2 - "build": invalid version specified: Invalid Semantic Version. You may need to use a different builder. Please check if the language version specified is supported by the os: ubuntu2204. You can refer to https://cloud.google.com/docs/buildpacks/builders for a list of compatible runtime languages per builder

(app.yaml configuration)
runtime: java21
instance_class: B2
manual_scaling:
    instances: 4
env_variables:
    SPRING_PROFILES_ACTIVE: "prod"

Observations
* No changes were made to my application code or configuration before this problem started.
* The exact same version was successfully deployed today at 2AM CEST
* This app.yaml configuration is in use for at least 3 months
* I cannot customise the versions in Standard App Engine as this service relies on existing runtimes

Has anyone else encountered similar issues with java21 runtime deployments?
Is this a known compatibility issue with the google-22 builder?
Any advice on resolving this or insights into potential workarounds would be greatly appreciated.

Thank you!

Best regards,

Aleksander Bartoszek

[nmagcalengjr]

Hi @ABartoszek,

Welcome to Google Cloud Community!

Here’s a quick guide to help you resolve the issue:

1. Retry your deployment: 

Given that infrastructure issues are often transient and may resolve automatically, as reported by others. The simplest and most common solution is to wait 15–30 minutes and then retry your deployment using the same configuration. If the issue occurred recently, simply redeploying with the same configuration might be enough to resolve it.

2. Check Google Cloud Status Dashboard:

If the issue reoccurs, record the timestamp and error details, then contact Google Cloud Support with relevant logs. Also, regularly monitor the Google Cloud Status Dashboard for any incidents involving App Engine, Cloud Build, or Java runtimes, as it's the primary source for updates on known or resolved service disruptions.

3. Check for gcloud CLI Updates:

Ensure your local gcloud CLI is up to date by running gcloud components update to stay compatible with the latest deployment processes. While an outdated CLI is unlikely to cause server-side build errors, keeping it current is a best practice.

Additionally, consider consulting with our Google Cloud Support for further guidance and assistance in reviewing your project setup.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.