Closed GoogleCodeExporter closed 8 years ago
I can deploy other apps using my same credentials to another project.
Original comment by Nicolas....@gmail.com
on 19 Apr 2016 at 1:33
Can you paste the full 403 error? Knowing at which phase of deployment you get
the 403 would be helpful here.
Original comment by z...@google.com
on 19 Apr 2016 at 3:06
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/citric-abbey-120520/builds?alt=js
on>: 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': 'Tue, 19 Apr 2016 15:37: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 Nicolas....@gmail.com
on 19 Apr 2016 at 3:38
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").
If you disable and re-enable the Container Builder API from the Cloud Console,
the service account should re-appear. Do you mind doing that and trying again?
Original comment by z...@google.com
on 19 Apr 2016 at 3:41
I was owner of the project but not listed also as editor. I added myself as
editor but the problem persists.
After re/enabling the Counter Build API it works now.
Thank you!!
Original comment by Nicolas....@gmail.com
on 19 Apr 2016 at 4:09
Thanks for keeping us updated; glad that it works now.
Original comment by z...@google.com
on 19 Apr 2016 at 4:19
Original issue reported on code.google.com by
Nicolas....@gmail.com
on 18 Apr 2016 at 10:23