hashicorp / terraform

Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
https://www.terraform.io/
Other
42.3k stars 9.49k forks source link

503 error getting Terraform state in USA #35613

Open billnbell3 opened 3 weeks ago

billnbell3 commented 3 weeks ago

Terraform Version

Latest version of Terraform local

Terraform Configuration Files

Same N/A

Debug Output

│ Error: Failed to request discovery document: 503 Service Unavailable

Expected Behavior

No error!

Actual Behavior

Error! Just today!

Steps to Reproduce

terraform init

Additional Context

N/A

References

N/A

liamcervante commented 3 weeks ago

Hi @billnbell3, are you able to share which backend you are using for state storage? The 503 Service Unavailable suggests the error is originating in a remote service and Terraform is simply reporting that.

If your backend is stored in S3, for example, this error is likely to have originated from AWS. If you are integrated with Terraform Cloud, then it could be TFC that is reporting the error.

We need a bit more information about your configuration / remote setup before we can start to debug this. Thanks!

billnbell3 commented 3 weeks ago

Yes it is terraform cloud that is giving 503

Get Outlook for iOShttps://aka.ms/o0ukef


From: Liam Cervante @.> Sent: Tuesday, August 20, 2024 1:12:14 AM To: hashicorp/terraform @.> Cc: Bill Bell @.>; Mention @.> Subject: Re: [hashicorp/terraform] 503 error getting Terraform state in USA (Issue #35613)

EXTERNAL: This message originated from outside of Exclusive Resorts. BE CAUTIOUS before clicking any links or attachments.

Hi @billnbell3https://github.com/billnbell3, are you able to share which backend you are using for state storage? The 503 Service Unavailable suggests the error is originating in a remote service and Terraform is simply reporting that.

If your backend is stored in S3, for example, this error is likely to have originated from AWS. If you are integrated with Terraform Cloud, then it could be TFC that is reporting the error.

We need a bit more information about your configuration / remote setup before we can start to debug this. Thanks!

— Reply to this email directly, view it on GitHubhttps://github.com/hashicorp/terraform/issues/35613#issuecomment-2298132211, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BIO6CBH3ADJG6P6H3236QRLZSLT45AVCNFSM6AAAAABMYVHXC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYGEZTEMRRGE. You are receiving this because you were mentioned.Message ID: @.***>

billnbell3 commented 3 weeks ago
terraform {
  # backend "s3" {
  #   bucket                  = "eks-karpenter-terraform"
  #   key                     = "dev"
  #   region                  = "us-east-1"
  #   shared_credentials_file = "~/.aws/credentials"
  # }

  cloud {
    organization = "exclusiveresorts"
    hostname = "app.terraform.io" # Optional; defaults to app.terraform.io
    workspaces {}
  }
}
sebasslash commented 3 weeks ago

:wave: @billnbell3, are you still encountering this issue? It could be related to the incident yesterday. That status page does not mention increased errors, but have confirmed with our platform team that customers were indeed seeing an increased number of errors.

And to double check here from your message above, were you attempting to perform a state migration?