Can't deploy changes in console: error response 13: An internal error occurred

[Victor Victor]

Hi!

I have added a friend in my Google Cloud project and gave her Owner, App Engine Admin, App Engine Deployer and App Engine Service Admin rights in IAM but when in her console she runs the command "gcloud app deploy" and tries to deploy the changes she made in her code in order to deploy her version, an error response 13: An internal error occurs. 

Can someone help us find a solution to this so that she will be able to deploy her changes to the live version?

[Ani Hatzis]

Ask her to try again now (since your post is already two hours old). However, if the problem persists, ask her to run the command with 

gcloud app deploy . --verbosity=debug 

to get more information about the potential reason.

There have been reports with this error code and message in this group previously. If a Mac was used somewhere in the process, the error might be caused by an "Icon?" file that was accidentally added to the application code / repository. See this post. In general, to avoid this kind of error in the future, it makes sense to define the skip_files directive in app.yaml.

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/62e862b1-0776-42b8-9217-c789b3d798db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[George (Cloud Platform Support)]

Hello Victor, 

It is not advisable to publish confidential information, such as project ID, in a public forum, with unrestricted visibility. I have deleted the image with confidential information. 

The issue seems to be caused by missing access rights. You project's logs show: 

"authorizationInfo: [

   0: {

    permission:  "resourcemanager.projectInvites.acceptProjectOwnership"     

    resource:  "projects/edited"     

   }

  ] "

This authorization attempt results in: 

"status: {

   code:  7    

   message:  "PERMISSION_DENIED"    

  }

 } "

You may consider simply granting your co-worker primitive roles such as Owner, Editor, and Viewer; these are simpler to use. 

How does your app.yaml look like? You should delete all confidential information from your reply. 

Does deployment cover files such as dos.yaml or dispatch.yaml? You may find more relevant information on the "Granting Project Access" page. 

[Victor Victor]

Thanks George!

Sorry about the images with confidential information. I did not knew they were actually confidential. 

Regarding user rights, are you referring to rights from IAM ? I think I gave her Owner rights. I also added some other rights just to be sure.

Regarding my yaml file, I have only one yaml file: app.yaml

 

[George (Cloud Platform Support)]

It may be worthwhile trying to only grant the primitive roles of Owner, Editor, and Viewer, and watch for any change in behavior when deploying. Does this happen only when deploying to update the default service? What happens if a new variant is deployed by the co-worker, distinct from the default service one?