ResourceErrorMessage: Timeout expired

[Adriano Matos]

I am trying to deploy MongoDB from the Marketplace. After setting up all my parameters for the VMs, I keep getting the following error message:

{“ResourceType”:“runtimeconfig.v1beta1.waiter”,“ResourceErrorCode”:“504”,“ResourceErrorMessage”:“Timeout expired.”}

From my googling, it seems to have something to do with my Compute Engine service account not having the necessary permissions. But what permissions do I need to give it? I can't find the documentation on this issue.

[George (Cloud Platform Support)]

Hello Adriano, 

You need to make sure your service enjoy is granted the Project Editor role. You may check the higly relevant posting by Fady. 

[Adriano Matos]

Hi George,

The service account in question already has that role enabled. I'll look into the thread you linked as well. Do you know if there are any other roles the service account needs?

Adriano

[Adriano Matos]

Actually, I can see the service account being used is a cloudservices.gserviceaccount.com (a service agent). However, I cannot find said service agent anywhere in my IAM or my list of service accounts so that I can add roles to it. Does the service agent know to use my compute engine service account?

Adriano

On Tuesday, March 15, 2022 at 12:01:44 PM UTC-7 George (Cloud Platform Support) wrote:

[Adriano Matos]

Apologies for all the messages. Just want to log what I am observing. I fixed the service agent not showing up. However, I still have the issue I mentioned in my first reply. The service account has the editor role, but I still get the timeout error.

Adriano

[Adriano Matos]

Just wanted to add this for anyone with this problem. I wasn't allocating enough resources to the VMs. Adding more RAM and CPU cores solved it.