Failures with Jumpstart Deployments

[bradykelly]

I didn't know where else to ask this, I can't seem to place it in any category because I know so little, having only started on GCP yesterday. 

I have now tried two of the Jumpstart deployments: The Python and JavaScript Web App and the Three Tier Web App. I set off the deployment for the first one and went away, only to return now to be told there were errors, I must see the logs, and delete the deployment and try again. I hadn't found the logs yet so I just deleted that deployment and proceeded to try again, but with the simpler looking 3 Tier Web App solution.

On this second attempt I got exactly the same message about errors, but I was able to find the logs, and this one error entry:

Exception calling IAM: There were concurrent policy changes. Please retry the whole read-modify-write with exponential backoff

I have no idea what this means as the jumpstart deployments seem to be supposed to handle everything automatically. I was given no instructions to configure anything before deploying, only a message that some configuration would be done for me.

[a_aleinikov]

Hi @bradykelly ,
You're right — Jumpstart deployments are supposed to handle most setup automatically. The error you saw usually happens when multiple changes are happening at the same time on IAM policies. It's not your fault — just bad timing. Deleting the deployment and trying again after a few minutes often fixes it. You're doing great for just starting on GCP!