DataLab Cloud Deployment 403 Error

问题:

I'm trying to deploy DataLab. Have confirmed my project is in a US zone. I've tried creating new projects and deploying there, to no avail. It appears everything works properly up to this point. Important to note, my project ID does not have the preceeding s~ (unsure if that matters or if it's simply a notation used in DataLab / Google Cloud. I have tried ~10 times over the course of two days with no success.

Nov  7 13:32:06 datalab-deploy-main-20151107-13-29-51 startupscript: Verifying that Managed VMs are enabled and ready.
Nov  7 13:32:06 datalab-deploy-main-20151107-13-29-51 startupscript: If this is your first deployment, this may take a while...#015If this is your first deployment, this may take a while...done.
Nov  7 13:32:06 datalab-deploy-main-20151107-13-29-51 startupscript: WARNING: If this is your first deployment, please try again.
Nov  7 13:32:06 datalab-deploy-main-20151107-13-29-51 startupscript: ERROR: (gcloud.preview.app.deploy) Server responded with code [403]:
Nov  7 13:32:06 datalab-deploy-main-20151107-13-29-51 startupscript:   Forbidden Unexpected HTTP status 403.
Nov  7 13:32:06 datalab-deploy-main-20151107-13-29-51 startupscript:   You do not have permission to modify this app (app_id=u's~datawranglingtest').
Nov  7 13:32:07 datalab-deploy-main-20151107-13-29-51 startupscript: Step deploy datalab module failed.

回答1:

It seems the permissions list are not synced between Developer Console and AppEngine. Try the following:

1. Go to Developer Console. Permissions page.
2. In the service account list, copy the account which looks like "******[e-mail]" to another place, and we'll use that later.
3. Make sure it disappears from the list. Then add the account back and make sure it has "Can edit" permissions.
4. Wait for a few minutes and try deploying Datalab again.

Meanwhile, the issue is probably project specific. If possible, you may also try it on a new project.

Let me know how it goes!

回答2:

Sorry to hear that. A few quick checks/questions --

1. Is your project billing enabled? This is needed for being able to instantiate managed VM instances within the project.

2. Are you a member of either the owners/editors groups within the project?

3. Is the Compute Engine API enabled. Specifically check on the status of the API at https://console.developers.google.com/apis/api/compute_component/overview?project=datawranglingtest

If these don't help, please let us know, and I'll get someone to look into your specific project.

The s~ prefix is used within AppEngine, and shouldn't be the source of this.