Cloud Run failing to deploy

[ahaboubi]

Hello,

I have a Cloud Run project that has been running for a couple of years now without any issues. I was able to successfully deploy a build yesterday morning. However, yesterday afternoon, I tried to deploy another build using "gcloud run deploy", but got this error message:

"(gcloud.run.deploy) FAILED_PRECONDITION: failed precondition: due to quota restrictions, cannot run builds in this region. Please contact support".

I'm deploying to northamerica-northeast2.

HELP!

Thanks.

[ahaboubi]

I'm still waiting for confirmation from the owner of the account, but I have a feeling that this has to do with an expired payment method. Would that cause this error message?

[footballfan]

Hi ahaboubi,

that's interesting, because I face the same issue now. In my case the region is europe-west3. I have checked the configured quotas and they look fine. There is also no problem with the payment account. In my case it worked for several months without any problems.

I hope we find a solution soon for this problem ...

BR F

[ahaboubi]

I followed the suggestion from @bentaylor and it worked for me.

[footballfan]

Yes, it works, great catch @bentaylor and thx @ahaboubi 
I used apt-get install google-cloud-cli=455.0.0-0 to downgrade on Debian.
However, I hope its a bug and not intended behavior ...

BR F

[bentaylor]

Try downgrading the CLI `gcloud components update --version 455.0.0`

I found this started happening after I ran `gcloud components update` which upgraded it to 456.0.0

I downgraded to 455.0.0 again and it deployed fine.

Check your version with `gcloud --version`

[Keshmirian]

Definitely looks like the latest release is bugged. Nice tip @bentaylor, thank you.

[frederikofamobi]

On the Google Cloud CLI version 456.0.0 it was added the following:

### Network Security

* Add `--billing-project` required flag to `gcloud network-security firewall-endpoints create` command to provide Google Cloud project ID for API enablement check, quota, and endpoint uptime billing.
* Add `--update-billing-project` flag to `gcloud network-security firewall-endpoints update` command to update the Google Cloud project used for API enablement check, quota, and endpoint uptime billing.

---

So it might be related.

And the --billing-account command seems like a beta feature:

---

(BETA) This command sets or updates the billing account associated with a project.

--billing-project=BILLING_PROJECTThe Google Cloud project that will be charged quota for operations performed in gcloud. If you need to operate on one project, but need quota against a different project, you can use this flag to specify the billing project. If both billing/quota_project and --billing-project are specified, --billing-project takes precedence. Run $ gcloud config set --help to see more information about billing/quota_project.

So I would recommend to set this value to your correct billing project, but even so, it feels like something is wrong from their side.

For more info: https://cloud.google.com/sdk/gcloud/reference/beta/billing/projects/link

[bentaylor]

Shouldn't need to pass a --billing-account flag to gcloud run deploy, because a project is already associated with a billing account.

Seems like having to give google information it should already know.

[ahaboubi]

That did it!

Thank you, @bentaylor 

[RashleyCape]

Me too!  Thank you!

[footballfan]

Hi, I just tried it again with version 458 and the behavior does not change, it still runs into the quota error. Is there an option to reopen the case, because on the long run it is no option to stay on 455?

BR F

[ahaboubi]

You're right. Even though @bentaylor 's suggestion worked, I don't think it's a permanent solution.

Hoping we can get some clarification as to why we're getting a quota error with cli versions after 455.0.0.

[inxtra]

doesn't work for me. No solution worked!

[ryusaychristo]

I can also confirm that the issue still remains in the 458.0.1; passing the billing-project CLA into the deploy command and manually linking the project to the billing account with the billing-account flag has no effect. Hopefully someone discovers a solution that doesn't involve downgrading to 455, though, many thanks to @bentaylor ; I'd still be banging my head against the wall otherwise.  👍

[ahaboubi · Accepted solution]

I upgraded to v460.0.0, and I can confirm that this issue is now fixed.