-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Comments
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! |
Yes it is terraform cloud that is giving 503
Get Outlook for iOS<https://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 @billnbell3<https://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 GitHub<#35613 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIO6CBH3ADJG6P6H3236QRLZSLT45AVCNFSM6AAAAABMYVHXC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYGEZTEMRRGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
👋 @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? |
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! |
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
The text was updated successfully, but these errors were encountered: