Fixed
Status Update
Comments
kn...@google.com <kn...@google.com> #2
Hi, thank you for submitting this issue. I already notified our engineering team about this case. Future update(s) will be posted here.
Meantime, you can use v186 until a fix is rolled out. Thanks
Meantime, you can use v186 until a fix is rolled out. Thanks
lu...@google.com <lu...@google.com> #3
Error is this one:
Error: Could not find or load main class com.google.appengine.tools.development.jetty9.QuickStartGenerator
Error: Could not find or load main class com.google.appengine.tools.development.jetty9.QuickStartGenerator
lu...@google.com <lu...@google.com> #4
It seems the Cloud SDK distro is missing this jar:
google-cloud-sdk/platform/google_appengine/google/appengine/tools/java/lib/tools/quickstart/quickstartgenerator.jar
But it is present in the classic GAE SDK fromhttps://cloud.google.com/appengine/docs/standard/java/download
google-cloud-sdk/platform/google_appengine/google/appengine/tools/java/lib/tools/quickstart/quickstartgenerator.jar
But it is present in the classic GAE SDK from
lu...@google.com <lu...@google.com> #5
A fix was done in our internal system.
Will show up in a next cloud SDK release.
For now, either move back to a previous cloud SDK build, or use the GAE Classic SDK which has the file in the correct place, so that the classic Maven plugin (based on Classic SDK) is still working.
Will show up in a next cloud SDK release.
For now, either move back to a previous cloud SDK build, or use the GAE Classic SDK which has the file in the correct place, so that the classic Maven plugin (based on Classic SDK) is still working.
pa...@gmail.com <pa...@gmail.com> #6
I got this error as well. After reverting the gcloud components to 186.0.0 the deployment worked. All I needed was to perform the following command: 'gcloud components update --version 186.0.0'
ca...@jcoder.io <ca...@jcoder.io> #7
Same here, got the same error and reverting back to 186 worked.
Is there a page where you publish known issues with the Cloud SDKs builds?
Is there a page where you publish known issues with the Cloud SDKs builds?
lu...@google.com <lu...@google.com> #8
Not aware of such a page.
The fix should be in the next Cloud SDK push on Wednesday, usually.
The fix should be in the next Cloud SDK push on Wednesday, usually.
pa...@gmail.com <pa...@gmail.com> #9
Temporary work around.
Today, the gcloud tool is at version 188.0.1 and the mvn deployments still don't work. Though I found a workaround.
As was mentioned about the GAE SDK in a comment on the 2nd of February. After downloading the sdk:
https://cloud.google.com/appengine/docs/standard/java/download
I copied the missing jar to the location that was mentioned:
cp -r appengine-java-sdk-1.9.62/lib/tools/quickstart [TO YOUR SDK PATH]google-cloud-sdk/platform/google_appengine/google/appengine/tools/java/lib/tools/
Subsequently, the mvn appengine:stage and mvn appengine:deploy worked as expected.
Today, the gcloud tool is at version 188.0.1 and the mvn deployments still don't work. Though I found a workaround.
As was mentioned about the GAE SDK in a comment on the 2nd of February. After downloading the sdk:
I copied the missing jar to the location that was mentioned:
cp -r appengine-java-sdk-1.9.62/lib/tools/quickstart [TO YOUR SDK PATH]google-cloud-sdk/platform/google_appengine/google/appengine/tools/java/lib/tools/
Subsequently, the mvn appengine:stage and mvn appengine:deploy worked as expected.
el...@google.com <el...@google.com> #10
Were all Java app deploys failing here or only some? If not all, what distinguished apps that could be deployed from ones that couldn't?
lu...@google.com <lu...@google.com> #11
All using a java8 web app with no web.xml or a web.xml pointing to a servlet 3.1 schema. No impact for Java7 apps, or using old servlet schemas.
But anyway, using Cloud SDK 190.0.1, it is now fixed.
But anyway, using Cloud SDK 190.0.1, it is now fixed.
pr...@shrewon.com <pr...@shrewon.com> #12
Same issue occurs with Google Cloud SDK 261.0.0
> gcloud --version
Google Cloud SDK 261.0.0
app-engine-java 1.9.76
app-engine-python 1.9.86
bq 2.0.47
cloud-datastore-emulator 2.1.0
core 2019.08.30
gcloud
gsutil 4.42
kubectl 2019.08.23
> gcloud --version
Google Cloud SDK 261.0.0
app-engine-java 1.9.76
app-engine-python 1.9.86
bq 2.0.47
cloud-datastore-emulator 2.1.0
core 2019.08.30
gcloud
gsutil 4.42
kubectl 2019.08.23
lu...@google.com <lu...@google.com> #13
1/ Did you tried the workaround?
2/ Can you share your web.xml?
2/ Can you share your web.xml?
Description
11:01:29 Error: Could not find or load main class com.google.appengine.tools.development.jetty9.QuickStartGenerator
11:01:29 Unable to stage app: Failed to generate quickstart-web.xml.
11:01:29 Please see the logs [/tmp/appcfg7616263863833710289.log] for further information.
11:01:29 :appengineStage FAILED
Log file contents
Unable to stage:
java.lang.RuntimeException: Failed to generate quickstart-web.xml.
at com.google.appengine.tools.admin.Application.createQuickstartWebXml(Application.java:1806)
at com.google.appengine.tools.admin.Application.populateStagingDirectory(Application.java:999)
at com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:872)
at com.google.appengine.tools.admin.AppAdminImpl.stageApplication(AppAdminImpl.java:539)
at com.google.appengine.tools.admin.AppAdminImpl.stageApplicationWithDefaultResourceLimits(AppAdminImpl.java:492)
at com.google.appengine.tools.admin.AppCfg$StagingAction.execute(AppCfg.java:2529)
at com.google.appengine.tools.admin.AppCfg.executeAction(AppCfg.java:390)
at com.google.appengine.tools.admin.AppCfg.<init>(AppCfg.java:213)
at com.google.appengine.tools.admin.AppCfg.<init>(AppCfg.java:119)
at com.google.appengine.tools.admin.AppCfg.main(AppCfg.java:115)
com.google.appengine.tools.admin.AdminException: Unable to stage app: Failed to generate quickstart-web.xml.
at com.google.appengine.tools.admin.AppAdminImpl.stageApplication(AppAdminImpl.java:543)
at com.google.appengine.tools.admin.AppAdminImpl.stageApplicationWithDefaultResourceLimits(AppAdminImpl.java:492)
at com.google.appengine.tools.admin.AppCfg$StagingAction.execute(AppCfg.java:2529)
at com.google.appengine.tools.admin.AppCfg.executeAction(AppCfg.java:390)
at com.google.appengine.tools.admin.AppCfg.<init>(AppCfg.java:213)
at com.google.appengine.tools.admin.AppCfg.<init>(AppCfg.java:119)
at com.google.appengine.tools.admin.AppCfg.main(AppCfg.java:115)
Caused by: java.lang.RuntimeException: Failed to generate quickstart-web.xml.
at com.google.appengine.tools.admin.Application.createQuickstartWebXml(Application.java:1806)
at com.google.appengine.tools.admin.Application.populateStagingDirectory(Application.java:999)
at com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:872)
at com.google.appengine.tools.admin.AppAdminImpl.stageApplication(AppAdminImpl.java:539)
The issue is not present in version 186.0.0-1 and jenkins is able to deploy to appengine after reverting google cloud sdk to 186.0.0
SO reference :