Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Precondition failed for billing account = bad error #1892

Closed
morgante opened this issue Aug 16, 2018 · 5 comments
Closed

Precondition failed for billing account = bad error #1892

morgante opened this issue Aug 16, 2018 · 5 comments

Comments

@morgante
Copy link

Affected Resource(s)

  • google_project

Expected Behavior

When I create a project and attempt to associate billing, if my billing account doesn't have sufficient quota I should get a "precondition failed error" which references that my quota is exhausted.

Actual Behavior

The error is "precondition failed" but doesn't specify what the failed precondition is.

Steps to Reproduce

Attempt to create a new project on a billing account (via Terraform) which doesn't have any quota left.

@nat-henderson
Copy link
Contributor

nat-henderson commented Aug 16, 2018

Does the error that comes back from the GCP API contain enough information to know that the error is related to exhausted quota? If you post debug logs I can go ahead and modify the output to be more helpful. :)

@morgante
Copy link
Author

morgante commented Aug 21, 2018

@ndmckinley I don't currently have a billing account with insufficient quota, but I do know that gcloud is able to return a verbose error in this case (similar to #1903).

@mattlawnz
Copy link

yes it does, here is the error:

- '@type': type.googleapis.com/google.rpc.QuotaFailure
  violations:
  - description: 'Cloud billing quota exceeded: https://support.google.com/code/contact/billing_quota_increase'
    subject: billingAccounts/REDACTED```

@emilymye
Copy link
Contributor

emilymye commented Jan 9, 2020

It looks like the API now returns a proper error message, so I'm going to close this and related issues.

@emilymye emilymye closed this as completed Jan 9, 2020
@ghost
Copy link

ghost commented Feb 9, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Feb 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants