The [Errno 13] Permission denied error has been reported a number of times 
on these issue links[1][2][3][4] and the errors were often obtained 
whenever an application is being deployed to App engine from a directory 
that is not parsable. Particularly in your case, we may require a lot more 
information to be able to advise you appropriately on the rootcause of the 
error obtained, which is why I recommend that you open an issue link[5] 
with a GCP Support engineer to further evaluate this issue with you. This 
type of inquiries are better addressed on the GCP issue tracker.

Please be sure to provide the verbosity debug logs of your gcloud app 
deploy command. That is, I recommend you attempt a new deploy using the 
verbosity flag set to debug levels, this will help to gather the verbosity 
logs[6] which usually provide all the details in an application deployment 
process and will help determine at what point the failure may have occurred.

The app deploy command with the verbosity flag would look like this: gcloud 
app deploy --verbosity=debug

I also recommend that you firstly update your CloudSDK to the latest 
version by using  ‘gcloud components update’[7] to ensure that the failure 
is not a result of older components in your CloudSDK.


[1] https://issuetracker.google.com/116173530
[2] https://issuetracker.google.com/72912382
[3] https://issuetracker.google.com/111931134
[4] https://issuetracker.google.com/75135380
[5] https://cloud.google.com/support/docs/issue-trackers#trackers-list
[6] https://cloud.google.com/sdk/gcloud/reference/config/set#verbosity
[7]https://cloud.google.com/sdk/gcloud/reference/components/update

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2f6dc953-efe0-4d3d-a87b-cdec9119d0fc%40googlegroups.com.

Reply via email to