-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Init concurrency/parallelism issues #2542
Comments
Hi,
I would suggest running |
If you're using Terraform >=1.4.0, you may specifically be running into problems related to changes made in the caching mechanism. |
@bushong1, How can I reproduce the issue locally? Could you please provide a configuration that produces this result? |
I'm running into this since upgrading from Terraform 1.2.9 to 1.4.5. I think the problem might be that Terragrunt isn't copying the provider lock file to the module cache directory it creates from a dependency when it fetches outputs from that dependency. Here are some debug logs from a run:
Interestingly, I have a mixture of successes and failures from dependencies using the same provider and version. I think this is due to the cache's weird parellelism issues. (We warm our provider cache out of band before running any Terragrunt to avoid this issue.)
I ran an inotifywait monitor on the cache directory of the dependency, and something in there is definitely concerning itself with the lockfile: Collapsed
|
I think I fixed it in #2568. |
Issue resolved in v0.45.12 release. |
Hi, |
I'm trying to track down some issues we've been having lately with what i believe is parallelism. We updated our environment to use a shared tf plugin cache path to cut down on directory size with all the provider binaries:
Since then, our directory size is much smaller, but we're running into a lot of issues with sporrattic init issues:
Setting paralleism to 4 seems to stop this from happening. Is this a known limitation with parallelism and shared plugin cache? I just can't figure out why my aws provider keeps on having checksum failures.
The text was updated successfully, but these errors were encountered: