google_project resource exits early leading to "Error: googleapi: Error 403: The project to be billed is associated with an absent billing account., accountDisabled"

[neurolabs]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

Terraform v0.12.26

• provider.archive v1.3.0
• provider.external v1.2.0
• provider.google v3.28.0

Affected Resource(s)

• google_project

Expected Behavior

after project is created, dependent resources can be created everytime

Actual Behavior

Sometimes, the apply run fails with "Error: googleapi: Error 403: The project to be billed is associated with an absent billing account., accountDisabled"

Steps to Reproduce

1. terraform apply

Important Factoids

References

• see google_project resource exits early leading to "Error: googleapi: Error 403: The project to be billed is associated with an absent billing account., accountDisabled" #5649, the fix did not introduce a timeout big enough.

[megan07]

Hi @neurolabs! I'm sorry you're still running into this issue. If I'm able, I'm hoping to find a better work around than increasing the sleep, however, I'm unable to reproduce it (even after commenting out the sleep) so I'm not sure what the responses look like and if there is something in the response I can key off of to see if we can retry, or do something different. Do you happen to have any debug logs I could look at to see what is exactly in these responses?
Thanks!

[edwardmedia]

@neurolabs feel free to reopen the issue if you see the issue again. Please share the debug log if you can. Thanks

[neurolabs]

@megan07 maybe you could somehow verify the connection to a billing account. in issue #6758 you can see that for the resource google_service_account, validation is done using the timeout concept.

[ghost]

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!