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

503 error getting Terraform state in USA #35613

Closed
billnbell3 opened this issue Aug 19, 2024 · 5 comments
Closed

503 error getting Terraform state in USA #35613

billnbell3 opened this issue Aug 19, 2024 · 5 comments
Labels
bug cloud Related to Terraform Cloud's integration with Terraform new new issue not yet triaged waiting for reproduction unable to reproduce issue without further information waiting-response An issue/pull request is waiting for a response from the community

Comments

@billnbell3
Copy link

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

@billnbell3 billnbell3 added bug new new issue not yet triaged labels Aug 19, 2024
@liamcervante
Copy link
Member

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!

@liamcervante liamcervante added the waiting-response An issue/pull request is waiting for a response from the community label Aug 20, 2024
@billnbell3
Copy link
Author

billnbell3 commented Aug 20, 2024 via email

@liamcervante liamcervante added cloud Related to Terraform Cloud's integration with Terraform and removed waiting-response An issue/pull request is waiting for a response from the community labels Aug 20, 2024
@billnbell3
Copy link
Author

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
Copy link
Contributor

👋 @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?

@crw crw added waiting-response An issue/pull request is waiting for a response from the community waiting for reproduction unable to reproduce issue without further information labels Aug 20, 2024
@jbardin
Copy link
Member

jbardin commented Oct 18, 2024

Since we have not heard back in a while I'm going to close the issue. If you have any updates regarding the issue, feel free to open a new issue with the requested information. If you have more questions, you can also use the community forum where there are more people ready to help.

Thanks!

@jbardin jbardin closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug cloud Related to Terraform Cloud's integration with Terraform new new issue not yet triaged waiting for reproduction unable to reproduce issue without further information waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

No branches or pull requests

5 participants