-
Notifications
You must be signed in to change notification settings - Fork 105
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
artifactory_permission_target fails to apply with error: Root object was present, but now absent. #988
Comments
@tpham-drw Thanks for the reporting. I've added this to our plan to investigate. |
@tpham-drw I noticed something in your HCL. Instead of using a plain text value for the repository ( e.g.
Using the plain text value means Terraform doesn't know The reference value will tell Terraform the dependency and will ensure it won't try to create the permission target until the repository is created first. As to why this works in dev (single node) vs QA/prod (3 nodes), this is probably because in a single node setup, the instance is (may be?) blocked during repository creating thus results in correct sequencing of resource creation. Whereas in multi-nodes setup, both resource creation API requests can be services simultaneously, thus results in this issue. At least this is my guess right now. |
@alexhung Thanks for the suggestion. I have tested both:
This still results in the TF applies failing:
I will test if running Terraform against a single node in the cluster will make a difference to the Terraform apply. |
@tpham-drw Thanks for the additional info. There were reports of same error message from other resources but I have not been able to reproduce them. My current suspicion is it has something to do with concurrency but more investigation is required. |
Hi @alexhung, I am in the process of testing using a endpoint without load balancing and ran into some issues with LDAP groups needing to be re-created/imported when the provider URL is changed. Do you know if updating the |
@tpham-drw I don't know for sure. I doubt it but it may be worth a try. |
Describe the bug
Terraform fails to apply
artifactory_permission_target
resource with errorRoot object was present, but now absent.
on the first attempt. Second attempt is successful.Full error message:
Requirements for and issue
Expected behavior
Resources are applied in a single Terraform apply run.
Additional context
We run into this issue in our QA and prod environments where we have a 3 node cluster. On dev, this is working without issues.
The issue seemingly started appearing when we added the
jfrog/platorm
provider to the repo alongside thejfrog/artifactory
provider.TF plan:
TF apply:
The text was updated successfully, but these errors were encountered: