Closed PaulBurridge closed 1 month ago
@levkohimins Happy to test a proposed fix when you have one, let me know if you need any more details.
@PaulBurridge, could you please provide a sample config to reproduce this issue?
@levkohimins Example repo here: https://github.com/PAB-me-uk/terragrunt-bug-3428
It is interesting that in my environment (Ubuntu 24.04.1 LTS) it works fine...
terragrunt run-all init --terragrunt-non-interactive --terragrunt-working-dir ./bad
[INFO] Getting version from tgenv-version-name
[INFO] TGENV_VERSION is 0.67.5
17:48:06.478 INFO The stack at ./bad will be processed in the following order for command init:
Group 1
- Module ./bbb/ccc/workspace
Group 2
- Module ./bbb/ccc/module-b
17:48:06.538 STDOUT [bbb/ccc/workspace] tofu: Initializing the backend...
17:48:06.578 STDOUT [bbb/ccc/workspace] tofu: Initializing provider plugins...
17:48:06.578 STDOUT [bbb/ccc/workspace] tofu: - Reusing previous version of hashicorp/null from the dependency lock file
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: - Using previously-installed hashicorp/null v3.2.3
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: OpenTofu has been successfully initialized!
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu:
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: You may now begin working with OpenTofu. Try running "tofu plan" to see
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: any changes that are required for your infrastructure. All OpenTofu commands
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: should now work.
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: If you ever set or change modules or backend configuration for OpenTofu,
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: rerun this command to reinitialize your working directory. If you forget, other
17:48:06.695 STDOUT [bbb/ccc/workspace] tofu: commands will detect it and remind you to do so if necessary.
17:48:06.757 STDOUT [bbb/ccc/module-b] tofu: Initializing the backend...
17:48:06.797 STDOUT [bbb/ccc/module-b] tofu: Initializing provider plugins...
17:48:06.797 STDOUT [bbb/ccc/module-b] tofu: - Reusing previous version of hashicorp/null from the dependency lock file
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: - Using previously-installed hashicorp/null v3.2.3
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: OpenTofu has been successfully initialized!
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu:
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: You may now begin working with OpenTofu. Try running "tofu plan" to see
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: any changes that are required for your infrastructure. All OpenTofu commands
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: should now work.
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: If you ever set or change modules or backend configuration for OpenTofu,
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: rerun this command to reinitialize your working directory. If you forget, other
17:48:06.930 STDOUT [bbb/ccc/module-b] tofu: commands will detect it and remind you to do so if necessary.
@PaulBurridge, thanks for the sample. Just tried it on MacOS, Terragrunt version 0.67.8, works fine, same output as @denis256. @PaulBurridge perhaps you missed something in the sample. What is your OS?
Although I have noticed one minor bug: file:///workspace/calypso/env-def-test
is converted to file://..
.
@PaulBurridge, It is also important for me to know the full path to the sample directory on your OS, this is important for accurate reproduction.
Running with absolute path
terragrunt run-all init --terragrunt-non-interactive --terragrunt-working-dir /workspace/test/terragrunt-bug-3428/bad
08:32:04.612 INFO The stack at . will be processed in the following order for command init:
Group 1
- Module ./bbb/ccc../../..
Group 2
- Module ./bbb/ccc/module-b
Copied into /tmp
terragrunt run-all init --terragrunt-non-interactive --terragrunt-working-dir /tmp/terragrunt-bug-3428/bad
08:32:15.651 INFO The stack at . will be processed in the following order for command init:
Group 1
- Module ./bbb/ccc/workspace
In dev container
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
I was wondering what was special about the module being called called workspace
so I assume this is related to the root directory being also called workspace
?
I was wondering what was special about the module being called called
workspace
so I assume this is related to the root directory being also calledworkspace
?
Correct. I was able to reproduce this behavior. I will fix it soon. Thanks for your cooperation.
Resolved in v0.67.12 release.
Describe the bug
Since #3400 module path logged in Group 1 has and incorrect path listed, also initial INFO entries related to "Retrieved output from" are missing.
Steps To Reproduce
Using source (but also happens with compiled version)
go run main.go run-all init --terragrunt-non-interactive --terragrunt-working-dir /workspace/redacted/environment-definitions/nonprod/na/projects/redacted/dev-na/us-east-2/databricks
Log:
Expected behavior
Log:
Versions
Additional context
Commits before #3400 and version 0.67.4 work as expected.