-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Provider Crash on parsing creation_time #12621
Comments
Here's an excerpt from the state file which shows that the integer reported in the output above as 'value out of range' is the creation_time:
Happy to provide more info if needed. |
@awatson72 what resource is it? |
@edwardmedia I don't believe this is related to one particular resource, I don't see an option to generate a debug log while running 'terraform plan'. No debug log, or crash log is generated, only the output to the screen which I pasted above.
And the provider config:
If the state file is needed, I would need to share that privately or do a bit of 'sanitization' |
Note that I have tried a bunch of different provider versions, including the newer 4.x versions - all have the same issue. |
@awatson72 it appears on the field |
It might be relevant to report the Windows version that I'm using WSL on Windows 10 21H2. |
Yep - I follow you. I assumed 'creation_time' applied to the whole state file, but let me dig deeper.... |
@awatson72 it is very likely. From the log you showed above, it has nothing to do with the provider |
ok, so it appears to be related to this resource:
The state file:
|
@awatson72 are you able to test run on a macbook to see if that happens? |
The issue does not occur on a macbook. |
This has come up in the past, #6518 / hashicorp/terraform-plugin-sdk#469 |
(whoops, just meant to click comment) |
Interesting - I'm using this terraform version:
On this WSL
For the most part, it works fine. I'll try a 64 bit version a terraform when I have chance. |
This issue is resolved when using the amd_64 version of terraform. So the takeaway is that Windows WSL users might be able to use the linux_386 version of terraform, but could have problems in certain circumstances.
|
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. |
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
1.2.9
Affected Resource(s)
N/A (All resources)
Terraform Configuration Files
N/A (Problem not related to configuration files)
N/A
Debug Output
Panic Output
N/A
Expected Behavior
Normal Terraform plan displayed
Actual Behavior
The above error
Steps to Reproduce
terraform plan
Important Factoids
Other Terraform directories / states on this laptop are fine - no issue.
References
The text was updated successfully, but these errors were encountered: