venf2k / google-cloud-sdk

Automatically exported from code.google.com/p/google-cloud-sdk
0 stars 0 forks source link

I am owner in this project but still cannot deploy sample app to project djsyndicationhub-dev #721

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Issue running command [gcloud preview app deploy].

What steps will reproduce the problem?

What is the expected output? What do you see instead?

Please provide any additional information below.

Trace:
googlecloudsdk/gcloud_main.py:169
 gcloud_cli.Execute()
googlecloudsdk/calliope/cli.py:654
 result = args.cmd_func(cli=self, args=ar...
googlecloudsdk/calliope/backend.py:1401
 resources = command_instance.Run(args)
surface/preview/app/deploy.py:507
 config_cleanup)
googlecloudsdk/api_app/deploy_command_util.py:195
 storage_client)
googlecloudsdk/api_app/deploy_command_util.py:245
 image.tag, cloudbuild_client)
googlecloudsdk/api_app/cloud_build.py:150
 logsBucket=logs_bucket,
googlecloudsdk/third_party/apis/cloudbuild/v1/cloudbuild_v1_client.py:198
 config, request, global_params=global_pa...
googlecloudsdk/third_party/apitools/base/py/base_api.py:708
 return self.ProcessHttpResponse(method_c...
googlecloudsdk/third_party/apitools/base/py/base_api.py:714
 self.__ProcessHttpResponse(method_config...
googlecloudsdk/third_party/apitools/base/py/base_api.py:586
 raise exceptions.HttpError.FromResponse(...
[output truncated]

Original issue reported on code.google.com by joshua.e...@dowjones.com on 11 Apr 2016 at 7:15

GoogleCodeExporter commented 8 years ago
Beginning deployment...

Verifying that Managed VMs are enabled and ready.
Building and pushing image for module [default]
ERROR: gcloud crashed (HttpError): HttpError accessing 
<https://cloudbuild.googleapis.com/v1/projects/djsyndicationhub-dev/builds?alt=j
son>: response: <{'status': '403', 'alternate-protocol': '443:quic', 
'content-length': '126', 'x-xss-protection': '1; mode=block', 
'x-content-type-options': 'nosniff', 'transfer-encoding': 'chunked', 'vary': 
'Origin, X-Origin, Referer', 'server': 'ESF', '-content-encoding': 'gzip', 
'cache-control': 'private', 'date': 'Mon, 11 Apr 2016 19:14:23 GMT', 
'x-frame-options': 'SAMEORIGIN', 'alt-svc': 'quic=":443"; ma=2592000; 
v="32,31,30,29,28,27,26,25"', 'content-type': 'application/json; 
charset=UTF-8'}>, content <{
  "error": {
    "code": 403,
    "message": "The caller does not have permission",
    "status": "PERMISSION_DENIED"
  }
}
>

Original comment by joshua.e...@dowjones.com on 11 Apr 2016 at 7:17

GoogleCodeExporter commented 8 years ago
This is just pushing the sample app as provided by google here: 
https://cloud.google.com/appengine/docs/flexible/nodejs/hello-world

Original comment by joshua.e...@dowjones.com on 11 Apr 2016 at 7:18

GoogleCodeExporter commented 8 years ago
Thanks for reporting this issue. It's unexpected behavior and we're tracking it 
internally.

I'll let you know if I get any updates on the status of the issue, or have a 
workaround for you.

Original comment by z...@google.com on 11 Apr 2016 at 7:34

GoogleCodeExporter commented 8 years ago
Can you verify that your project has a cloudbuild.gserviceaccount.com service 
account with EDITOR permissions? You can do this by navigating to the Cloud 
Console > Permissions page (the name you see may be slightly different, like 
"Admin").

Original comment by z...@google.com on 11 Apr 2016 at 10:19

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
If you disable and re-enable the Cloud Build API, the service account should 
re-appear. Do you mind doing that and trying again?

Original comment by z...@google.com on 12 Apr 2016 at 4:35

GoogleCodeExporter commented 8 years ago
Which API is that specifically?  I don't see anything called "Cloud Build API" 
in our available APIs for this project...

Original comment by joshua.e...@dowjones.com on 12 Apr 2016 at 4:49

Attachments:

GoogleCodeExporter commented 8 years ago
Sorry, I mis-typed. Container Builder is the one you want.

Original comment by z...@google.com on 12 Apr 2016 at 4:50

GoogleCodeExporter commented 8 years ago
Excellent.  Disabling/enabling the API fixed the issue.  I'm guessing some 
overzealous admin removed the permissions without realizing the impact.

Thanks for the quick response and help!

Original comment by joshua.e...@dowjones.com on 12 Apr 2016 at 4:58

GoogleCodeExporter commented 8 years ago
Glad you were able to get it working! We're looking into a way we can protect 
these special service accounts from exactly that happening in the future, but 
that's on the backend side of things so I'm going to close this issue out.

Original comment by z...@google.com on 12 Apr 2016 at 5:00