I'll also add that if you have Gold support on one project it's valid for
both if they are under the same billing account, so your best route is
likely opening a support case.
On Tuesday, January 19, 2016 at 6:51:01 PM UTC-5, Adam (Cloud Platform
Support) wrote:
>
> If it's local to the project
If it's local to the project, I'd start by checking the metadata for each
project for discrepancies and also note the region you are using to create
instances. Check the GCE quota details for limits as this also will affect
your ability to create Managed VM instances.
On Monday, January 18, 201
I already tried deleting all versions/instances, but it did not help.
Deploying the same code to a completely new project worked. What can be the
cause? Both projects are on the same billing account. The only difference I
can think of as relevant is the SSL resource that I created for compute
engi
The only recommendation I have is to try deleting all versions of Managed
VM modules from App Engine -> Versions, and also any remaining Managed VM
instances from Compute Engine -> Instances and trying a redeploy. I don't
have any reports of known issues with Managed VM deployments at this time
1. I tried to redeploy all modules. The default is App Engine instances,
and it works fine. The backend module is managed VMs, and it refuses to
deploy. It worked yesterday.
2. When I try to deploy (gcloud preview app deploy), I get an error
message, including , but I do see the age-builder instan
Does this happen for non-default modules or the default module? If
non-default, have you tried re-deploying the default module to a new
version as well? Under 'Compute Engine' -> VM instances, do you see many
'gae-*' instances in an unhealthy state (including any gae-builder
instances)?
On Fri
