managed-vm

GAE Managed VM with automatic scaling and resources config fails with HttpError 409

三世轮回 提交于 2020-01-05 14:11:27
问题 I'm experiencing the following error intermittently while deploying a java application to appengine using managed VMs with explicit resource configuration: Deployment failed: https://www.googleapis.com/autoscaler/v1beta2/projects/managedvm409example/zones/us-central1-f/autoscalers?alt=json returned "Autoscaler resource with this name already exists in this zone or there exists an Autoscaler controlling the given target."> Deployed Version: 1.385892435190233331 Here's the configuration I'm

GAE Managed VM with automatic scaling and resources config fails with HttpError 409

孤街浪徒 提交于 2020-01-05 14:11:20
问题 I'm experiencing the following error intermittently while deploying a java application to appengine using managed VMs with explicit resource configuration: Deployment failed: https://www.googleapis.com/autoscaler/v1beta2/projects/managedvm409example/zones/us-central1-f/autoscalers?alt=json returned "Autoscaler resource with this name already exists in this zone or there exists an Autoscaler controlling the given target."> Deployed Version: 1.385892435190233331 Here's the configuration I'm

Undocumented Managed VM task queue RPCFailedError

六眼飞鱼酱① 提交于 2020-01-02 08:35:40
问题 I'm running into a very peculiar and undocumented issue with a GAE Managed VM and Task Queues. I understand that the Managed VM service is in beta, so this question may not be relevant forever, but it's definitely causing me lots of headache now. The main symptom of the issue is that, in certain (not completely known to me) circumstances, I'm seeing the following error/traceback: File "/home/vmagent/my_app/some_file.py", line 265, in some_ndb_tasklet res = yield some_task.add_async('some-task

“Failed to import google/appengine/ext/deferred/handler.py” in Google App Engine Flexible Environment

▼魔方 西西 提交于 2019-12-23 15:33:09
问题 I use App Engine Flexible Environment (previously called Managed VMs), and recently upgraded to the latest gcloud SDK. It included some new errors: ERROR: (gcloud.preview.app.deploy) Error Response: [400] Invalid character in filename: lib/setuptools/script (dev).tmpl ERROR: The [application] field is specified in file [.../app.yaml]. This field is not used by gcloud and must be removed. Project name should instead be specified either by `gcloud config set project MY_PROJECT` or by setting

Appengine deployments are extraodinarily slow today?

柔情痞子 提交于 2019-12-22 18:34:20
问题 We have a small java project need to deploy it include 9000+ files command : mvn gcloud:deploy but I get the Log: ... [INFO] INFO: Uploading [/home/steven/work/idigisign/target/appengine-staging/__static__/node_modules/rx/src/core/linq/observable/when.js] to [7dfb30ad32893c5042dba03601f006a40419fab0] [INFO] DEBUG: Uploading [/home/steven/work/idigisign/target/appengine-staging/assets/global/plugins/bootstrap-switch/js/bootstrap-switch.min.js] to [7e0725897d7b99c3c33b56915d202e2dde552ea9]

My java App Engine Managed VMs build doesn't deploy after 4/14/2015 update

佐手、 提交于 2019-12-19 04:06:19
问题 My java App Engine Managed VMs build doesn't deploy any more using gcloud preview app deploy target/myapp-SNAPSHOT I get this: ERROR: Found no valid App Engine configuration files in directory 回答1: The usage of gcloud preview app deploy changed in our gcloud 2015.04.14 release, you now have to specify the .yaml file for your module as well as --project projectID . The documentation should be updated shortly. For Java, we've released an updated maven plugin. In your pom.xml, please add the

Failure deploying AppEngine version because of Cloud Storage JSON API enablement

こ雲淡風輕ζ 提交于 2019-12-11 05:01:03
问题 I am trying to deploy to Google AppEngine. (More precisely: Managed VM.) I ran gcloud preview app deploy d:\dev\mytest\yaml-war\app.yaml --version=joshua20160316d --project=mytest-test1 . After about 30 minutes, it failed. The error message directs me to log lines in the Cloud Developer Console (see below) which tell me that access to the Cloud Storage JSON API needs to be enabled. However, the Developer Console shows that the Cloud Storage JSON API is already enabled. (See screenshot.) Also,

Cannot seem to install Google Cloud Managed VMs

本小妞迷上赌 提交于 2019-12-10 10:28:10
问题 Following Google instructions to install managed VMs, everything seems to work smoothly until I get to this step: gcloud preview app setup-managed-vms The result is the following error: ERROR: (gcloud.preview.app) Invalid choice: 'setup-managed-vms'. I've made sure all the other dependent components are up to date. The environment is: Windows 7 x64 Google Cloud SDK 0.9.56 boot2docker 1.4.1/1.5 (tried both) Is there anything obvious I'm missing trying to get these managed VMs working? 回答1: Yep

Appengine deployments are extraodinarily slow today?

▼魔方 西西 提交于 2019-12-06 10:37:48
We have a small java project need to deploy it include 9000+ files command : mvn gcloud:deploy but I get the Log: ... [INFO] INFO: Uploading [/home/steven/work/idigisign/target/appengine-staging/__static__/node_modules/rx/src/core/linq/observable/when.js] to [7dfb30ad32893c5042dba03601f006a40419fab0] [INFO] DEBUG: Uploading [/home/steven/work/idigisign/target/appengine-staging/assets/global/plugins/bootstrap-switch/js/bootstrap-switch.min.js] to [7e0725897d7b99c3c33b56915d202e2dde552ea9] [INFO] INFO: Uploading [/home/steven/work/idigisign/target/appengine-staging/assets/global/plugins

Cannot seem to install Google Cloud Managed VMs

拈花ヽ惹草 提交于 2019-12-06 00:24:41
Following Google instructions to install managed VMs , everything seems to work smoothly until I get to this step: gcloud preview app setup-managed-vms The result is the following error: ERROR: (gcloud.preview.app) Invalid choice: 'setup-managed-vms'. I've made sure all the other dependent components are up to date. The environment is: Windows 7 x64 Google Cloud SDK 0.9.56 boot2docker 1.4.1/1.5 (tried both) Is there anything obvious I'm missing trying to get these managed VMs working? Les Vogel - Google DevRel Yep - that step is no longer required. The docs should be fixed shortly. You might