Skip to content
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

[Bug]: Regression in 5.39.0 #36056

Closed
tschmidty69 opened this issue Mar 1, 2024 · 4 comments · Fixed by #36054
Closed

[Bug]: Regression in 5.39.0 #36056

tschmidty69 opened this issue Mar 1, 2024 · 4 comments · Fixed by #36054
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@tschmidty69
Copy link

Terraform Core Version

1.7.1

AWS Provider Version

5.39.0

Affected Resource(s)

EC2 instance, specifically reading ebs tags_all

Expected Behavior

Reads happen properly

Actual Behavior


│ Error: reading EC2 Instance (i-123456789): reading EC2 Instance (i-123456789): Invalid address to set: []string{"ebs_block_device", "0", "tags_all"}

│ with module.environment_stg.module.ebs_volumes["ec2"].data.aws_instance.attachment_target,
│ on .terraform/modules/environment_stg.ebs_volumes/main.tf line 1, in data "aws_instance" "attachment_target":
│ 1: data "aws_instance" "attachment_target" {

Relevant Error/Panic Output Snippet

╷
│ Error: reading EC2 Instance (i-123456789): reading EC2 Instance (i-123456789): Invalid address to set: []string{"ebs_block_device", "0", "tags_all"}
│ 
│   with module.environment_stg.module.ebs_volumes["ec2"].data.aws_instance.attachment_target,
│   on .terraform/modules/environment_stg.ebs_volumes/main.tf line 1, in data "aws_instance" "attachment_target":
│    1: data "aws_instance" "attachment_target" {
│ 
╵

Terraform Configuration Files

There is a lot of code associated with this and very specific to my use case which would be a great deal of work to anonymize. In any case since it works with 5.38.0 and not with 5.39.0 it does not seem entirely necessary.

Steps to Reproduce

Running this plan with 5.39.0 results in the above errors, 5.38.0 plans and applies properly.

Debug Output

No response

Panic Output

No response

Important Factoids

Seems to be a duplicate of this bug #17125

References

My best guess is one of these commits from @YakDriver who also fixed the previous bug (possible duplicate/regression) #17125

c9769c9
4c3e2c5

Would you like to implement a fix?

None

@tschmidty69 tschmidty69 added the bug Addresses a defect in current functionality. label Mar 1, 2024
@github-actions github-actions bot added the service/ec2 Issues and PRs that pertain to the ec2 service. label Mar 1, 2024
Copy link

github-actions bot commented Mar 1, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Mar 1, 2024
@YakDriver
Copy link
Member

Thank you for raising this. This is fixed by #36054 and will be available in v5.39.1.

@terraform-aws-provider terraform-aws-provider bot removed the needs-triage Waiting for first response or review from a maintainer. label Mar 1, 2024
@YakDriver YakDriver added this to the v5.39.1 milestone Mar 1, 2024
Copy link

github-actions bot commented Mar 6, 2024

This functionality has been released in v5.39.1 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

github-actions bot commented Apr 6, 2024

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants