-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Crash error: Root resource was present, but now absent. #8128
Crash error: Root resource was present, but now absent. #8128
Comments
@chaopeng The information you provided isn't adequate enough to understand the issue . We need to know what resource is failing and provide the debug log to help us identify where its filling? Please also provide the specific resource config or plan output to repro the issue on our end |
Hi, I am also running into this error. With the tf script being:
I get the following error:
|
I was able to reproduce the same issue with the following configs. My Terraform version is 0.14.4. And I think the same issue occurs with Terraform 0.13 as well. The project itself matters. If a dataset has been successfully created in a project before, then the issue seems do not occur. So to reproduce the issue, create a new project every time.
|
I can also reproduce the error with just the
|
My guess is such safety check was introduced in Terraform 0.12 as https://www.terraform.io/docs/extend/terraform-0.12-compatibility.html#inaccurate-plans but not enforced so this resource was fine with Terraform 0.12. However, it's likely since Terraform 0.13, such safety check is enforced and a fix needs to be implemented for the |
Logs when I set TF_LOG=DEBUG
|
The dataset was actually created successfully, but Terraform's GET call to verify it's created failed due to dataset not initialized . I guess some sort of retry logic should be implemented to retry the GET request so it doesn't fail and just exit in the first attempt. |
@venkykuberan @rileykarson have you seen similar issue before? I can take a stab in fixing this, but might need some guidance from you or existing examples for how to add retry logics for a resource in magic-module. |
Browsing the magic module repo and found something like https://github.com/GoogleCloudPlatform/magic-modules/blob/d910e58b30b67e1c641463ab56de084ed4351225/products/pubsub/terraform.yaml#L32 plus https://github.com/GoogleCloudPlatform/magic-modules/blob/master/third_party/terraform/utils/error_retry_predicates.go. Trying something similar for healthcare dataset. |
Worked. Sent GoogleCloudPlatform/magic-modules#4412 |
The fix is planned to be released in google provider 3.54.0 next Monday. |
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 👉 [email protected]. Thanks! |
I have see a when "Root resource was present, but now absent." error when upgrade the version of terraform-provider-google to 3.51.0
In this PR terraform-google-modules/terraform-google-healthcare#36
Community Note
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 tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
I don't know yet. It seems related to
google_healthcare_dataset
Terraform Configuration Files
https://github.com/terraform-google-modules/terraform-google-healthcare/blob/master/examples/simple_example/main.tf
Debug Output
Panic Output
https://github.com/terraform-google-modules/terraform-google-healthcare/pull/36/checks?check_run_id=1658019589
Expected Behavior
No error
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: