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

Multiple AWS Providers results in: err="rpc error: code = Unavailable desc = transport is closing" #19512

Open
Doug-North opened this issue May 25, 2021 · 2 comments
Labels
provider Pertains to the provider itself, rather than any interaction with AWS. upstream-terraform Addresses functionality related to the Terraform core binary. waiting-response Maintainers are waiting on response from community or contributor.

Comments

@Doug-North
Copy link

In my workspace I am defining multiple AWS providers for different accounts.

provider "aws" {
  region = "eu-west-2"
  alias  = "example1"
  assume_role {
    role_arn = "arn:aws:iam::ACCOUNT-ID:role/ROLE-NAME"
  }
}

Everything works fine until i get to around 5 providers, when I receive the error:

Error: rpc error: code = Canceled desc = context canceled

Attached is an exert of the debug output, confirming it is indeed the AWS Provider that is failing
debug-output.log

I have removed a few providers, and dependent resources from the state as a 'workaround'

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label May 25, 2021
@ewbankkit ewbankkit added provider Pertains to the provider itself, rather than any interaction with AWS. upstream-terraform Addresses functionality related to the Terraform core binary. labels May 25, 2021
@soleares
Copy link
Contributor

soleares commented Jun 2, 2021

It looks like you're getting this with 3.42.0. I'm getting this error a lot. I've tried with versions 3.40.0 and 3.43.0. I'm also using assume_role in my aws provider.

@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 3, 2021
@justinretzolk
Copy link
Member

Hey @Doug-North 👋 Thank you for taking the time to raise this! In the past (when I used to support Terraform Cloud and Terraform Enterprise), when I've seen this type of error message, it usually was caused by the machine that Terraform was running on running out of memory. Given that this happened when you added additional instances of the AWS provider, and went away when you removed those, it seems as though that may be the case here. I realize it's been a while, but are you able to monitor the machine to see if that is indeed the case?

@justinretzolk justinretzolk added the waiting-response Maintainers are waiting on response from community or contributor. label May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
provider Pertains to the provider itself, rather than any interaction with AWS. upstream-terraform Addresses functionality related to the Terraform core binary. waiting-response Maintainers are waiting on response from community or contributor.
Projects
None yet
Development

No branches or pull requests

5 participants