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]: Issue with Latest Terraform AWS Provider Version v5.71.0 #1 #39681

Closed
manesanket11 opened this issue Oct 11, 2024 · 8 comments
Closed
Labels
bug Addresses a defect in current functionality. provider Pertains to the provider itself, rather than any interaction with AWS.

Comments

@manesanket11
Copy link

Terraform Core Version

v1.9.5

AWS Provider Version

v5.71.0

Affected Resource(s)

Installing hashicorp/aws v5.71.0...

│ Error: Failed to install provider

│ Error while installing hashicorp/aws v5.71.0: archive has incorrect
│ checksum
│ zh:21f5d77f2859d9ddb5fafa7b6cfd0efdf82977c631ce788e56728afc6da17323
│ (expected
│ zh:c164d3ed13eb4c28ac243221591fc4ac3cfe621f8cd20af[53]

Expected Behavior

It should not give this error

Actual Behavior

Hello Everyone,

Looks like there is an issue with the Latest Terraform AWS Provider Version v5.71.0. I am getting below error while executing terraform code. it works fine when I set the provider version to the hashicorp/aws v5.70.0

Installing hashicorp/aws v5.71.0...

│ Error: Failed to install provider

│ Error while installing hashicorp/aws v5.71.0: archive has incorrect
│ checksum
│ zh:21f5d77f2859d9ddb5fafa7b6cfd0efdf82977c631ce788e56728afc6da17323
│ (expected
│ zh:c164d3ed13eb4c28ac243221591fc4ac3cfe621f8cd20af[53]

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

terraform {
required_providers {
aws = {
source = "hashicorp/aws"
}
}
}

Steps to Reproduce

terraform {
required_providers {
aws = {
source = "hashicorp/aws"
}
}
}

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@manesanket11 manesanket11 added the bug Addresses a defect in current functionality. label Oct 11, 2024
Copy link

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.

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Oct 11, 2024
@anmolsha-te
Copy link

This issue is duplicate of #39676

@reixd
Copy link

reixd commented Oct 11, 2024

Quick workaround until filxed

provider "aws" {
  region = var.region
  version = "< 5.71.0"
}

@bassmanitram
Copy link

Needless to say, but just in case of any confusion, this occurs for any version of Terraform that can use V5 of the AWS provider.

@ewbankkit ewbankkit added provider Pertains to the provider itself, rather than any interaction with AWS. and removed needs-triage Waiting for first response or review from a maintainer. labels Oct 11, 2024
@justinretzolk
Copy link
Member

Copying over my comment from #39676:

Hey everyone 👋 Thank you very much for taking the time to raise this, and for adding reactions to help ensure it was brought to our attention -- that's extremely helpful. We ran into an issue with our release process that led to this, and so have pulled the 5.71.0 release to resolve the immediate issue. We're working through the release issue internally, and will make a new release once we're confident that it has been resolved.

Since the issue reported here has been resolved, I'm going to close this issue out. Thank you again to all who reported -- if you run into issues in the future, please do continue to let us know!

Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@myshon
Copy link

myshon commented Oct 15, 2024

image
I suggest extending weekends for employees, not for simple bugs. 😉 Can't wait for the patch—really don’t want to be fixing multiple pipelines myself.

Copy link

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 Nov 15, 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. provider Pertains to the provider itself, rather than any interaction with AWS.
Projects
None yet
Development

No branches or pull requests

7 participants