Managed VM: Confusion over Disk-Size and App Space Usage

[GoogleCodeExporter]

What steps will reproduce the problem?
I tried deploying my Google App Engine App to Managed VM. Because it's an app 
engine app and I don't use the disk, I initially set my required disk space to 
1GB.

What do you see?
The deployment fails.

Please provide any additional information below.
There are two issues here.

At the time, it was unclear (now clear in retrospect), that your own app 
requires disk space. If you have a 2GB app, and you specify only 1GB of disk 
space, then the deployment fails with this cryptic error message:

       Error synchronizing files. Return code: 1. Retrying.

It would be nice if it told you that it failed because you set your disk size 
too small.

After I figured that out, I set my disk size to 5GB. At the very end of the 
deployment process (which takes several minutes), it told me my disk had to be 
at least 10GB. This was a nice error message, but it would have been nicer if 
it told me that at the start of the deployment process, not at the end. 

This is not a true bug, but it would make using managed vm for the first time a 
lot smoother.

Original issue reported on code.google.com by michael....@docketalarm.com on 10 Mar 2016 at 1:28

[GoogleCodeExporter]

Thank you very much for the detailed feedback. We will work on providing better 
error messages in this scenario.

Original comment by vil...@google.com on 11 Mar 2016 at 12:13

• Changed state: Accepted

[GoogleCodeExporter]

Could you paste the output of "gcloud info"?

I think the error was actually unrelated to disk size, and you just got lucky 
the second time.

Original comment by dlor...@google.com on 11 Mar 2016 at 12:14

[GoogleCodeExporter]

I've retracted some of the personal info with X's, but let me know if you need 
it.

Google Cloud SDK [95.0.0]

Platform: [Windows, x86_64]
Python Version: [2.7 (r27:82525, Jul  4 2010, 09:01:59) [MSC v.1500 32 bit 
(Intel)]]
Python Location: [c:\Python27\python.exe]
Site Packages: [Disabled]

Installation Root: [C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk]
Installed Components:
  core: [2016.01.29]
  app-engine-python: [1.9.31]
  bq-win: [2.0.18]
  core-win: [2016.01.12]
  gcloud: []
  windows-ssh-tools: [2016.01.29]
  beta: [2016.01.12]
  gsutil: [4.16]
  bq: [2.0.18]
  gsutil-win: [4.16]
System PATH: [C:\Program Files (x86)\Google\Cloud 
SDK\google-cloud-sdk\bin\..\bin\sdk;C:\Program 
Files\ImageMagick-6.9.3-Q16-HDRI;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\
system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShe
ll\v1.0\;C:\Program Files\Ethereum 0.9.41\bin;C:\Program Files 
(x86)\Skype\Phone\;C:\Program Files (x86)\Tesseract-OCR;C:\Program Files 
(x86)\Google\Cloud 
SDK\google-cloud-sdk\bin;c:\Python27;C:\Python27\Scripts;C:\cygwin\bin;C:\Users\
XXXXXXX\AppData\Local\Programs\Git\cmd;]
Cloud SDK on PATH: [True]

Installation Properties: [C:\Program Files (x86)\Google\Cloud 
SDK\google-cloud-sdk\properties]
User Config Directory: [C:\Users\XXXXXXX\AppData\Roaming\gcloud]
User Properties: [C:\Users\XXXXXXX\AppData\Roaming\gcloud\properties]
Current Workspace: [None]
Workspace Config Directory: [None]
Workspace Properties: [None]

Account: [XXXXXXX]
Project: [XXXXXXX]

Current Properties:
  [core]
    project: [XXXXXXX]
    account: [XXXXXXX]
    disable_usage_reporting: [False]
  [app]
    promote_by_default: [false]
    use_cloud_build: [True]
    suppress_change_warning: [true]
  [compute]
    region: [us-central1]
    zone: [us-central1-f]

Logs Directory: [C:\Users\XXXXXXX\AppData\Roaming\gcloud\logs]
Last Log File: 
[C:\Users\XXXXXXX\AppData\Roaming\gcloud\logs\2016.03.10\20.14.22.295000.log]

Original comment by michael....@docketalarm.com on 11 Mar 2016 at 1:18

[GoogleCodeExporter]

Thanks.  The error you got was actually a result of uploading your application 
files to Google Cloud Storage before the deployment. It was not caused by the 
disk size of your Managed VM. We've made some reliability improvements to this 
upload flow in recent weeks, so you'll probably see this error a lot less often 
if you run "gcloud components update" to get to the latest version.

Please reopen this if you still see any errors like this after updating!

Original comment by dlor...@google.com on 12 Mar 2016 at 1:23

[GoogleCodeExporter]

Original comment by dlor...@google.com on 12 Mar 2016 at 1:23

• Changed state: Obsolete