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.

Sign up for GitHub

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

Jump to bottom

[Bug]: hashicorp/aws 5.65.0 failing to pull on terraform init after morning of 10/14/24 #39725

Open
jasonm3-netapp opened this issue Oct 15, 2024 · 2 comments
Open

[Bug]: hashicorp/aws 5.65.0 failing to pull on terraform init after morning of 10/14/24 #39725

jasonm3-netapp opened this issue Oct 15, 2024 · 2 comments
Labels
bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. waiting-response Maintainers are waiting on response from community or contributor.

Comments

@jasonm3-netapp
Copy link

jasonm3-netapp commented Oct 15, 2024 •
edited by justinretzolk
Loading

Terraform Core Version

1.9.7

AWS Provider Version

5.65.0

Affected Resource(s)

No response

Expected Behavior

"terraform init" should pass. We've been pinned to 5.65.0 for a while now, but suddenly it began to fail yesterday morning (10/14/24) when you pulled 5.71.0.

Actual Behavior

All of our pipelines that use the AWS provider are now failing.

Relevant Error/Panic Output Snippet

│ Error: Failed to query available provider packages
│ 
│ Could not retrieve the list of available versions for provider
│ hashicorp/aws: no available releases match the given constraints >= 2.23.0,
│ >= 3.27.0, >= 3.29.0, >= 3.70.0, >= 3.72.0, >= 4.0.0, >= 4.9.0, >= 4.19.0,
│ >= 4.21.0, >= 4.22.0, >= 4.33.0, >= 4.36.0, >= 4.40.0, >= 4.54.0, >=
│ 4.57.0, >= 4.59.0, >= 4.63.0, >= 4.64.0, >= 4.66.0, >= 5.0.0, >= 5.9.0, >=
│ 5.27.0, >= 5.61.0, >= 5.65.0, 5.65.0, >= 5.70.0
╵

Error: Terraform exited with code 1.
Error: Process completed with exit code 1.

Terraform Configuration Files

terraform {
  required_version = ">= 1.0"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "5.65.0"
    }
    kubernetes = {
      source  = "hashicorp/kubernetes"
      version = "2.19.0"
    }
    helm = {
      source  = "hashicorp/helm"
      version = "2.9.0"
    }
    spotinst = {
      source  = "spotinst/spotinst"
      version = "1.115.0"
    }
    local = {
      version = "~> 2.1"
    }
    github = {
      source  = "integrations/github"
      version = "6.2.3"
    }
  }
}

Steps to Reproduce

Pin to version 5.65.0 of the AWS provider.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None
@jasonm3-netapp jasonm3-netapp added the bug Addresses a defect in current functionality. label Oct 15, 2024
@github-actions GitHub Actions
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 15, 2024
@justinretzolk
Copy link
Member

Hey @jasonm3-netapp 👋 Thank you for taking the time to break this out into a separate issue, and for providing that extra information. I think I see where your issue is coming from. Looking at the error you posted, it includes >= 5.70.0, which would exclude 5.65.0.

Based on the output, I suspect you've got a module that has version constraints that may have been updated around the same time. Can you check and see if that's the case?

@justinretzolk justinretzolk added the waiting-response Maintainers are waiting on response from community or contributor. label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. waiting-response Maintainers are waiting on response from community or contributor.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@justinretzolk @jasonm3-netapp