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

Crash on TF refresh (going from Windows to Mac machine) #21816

Closed
tiesmaster opened this issue Jun 20, 2019 · 2 comments
Closed

Crash on TF refresh (going from Windows to Mac machine) #21816

tiesmaster opened this issue Jun 20, 2019 · 2 comments

Comments

@tiesmaster
Copy link

Terraform Version

➜  infra git:(269/infra) ✗ terraform --version
Terraform v0.12.2
+ provider.azuread v0.4.0
+ provider.azurerm v1.30.1
+ provider.random v2.1.2

Terraform Configuration Files

See this Gist.

Crash Output

See this Gist.

Expected Behavior

Refresh the state.

Actual Behavior

Crashed the system.

Steps to Reproduce

This is what I did:

  1. git pull to get my latest changes from what I had on Windows.
  2. export ARM_ACCESS_KEY=... to set my azurerm backend access key
  3. tf init, initialized correctly
  4. tf refresh, crashed the system

Additional Context

We're starting to use Terraform here at Buddy Payment. We're adopting it in small steps, so first, we're still using it from the command-line (as opposed to straight from a CI/CD pipeline). We've just went from local state to remote state using the azurerm backend.

In this scenario, I started to use it from a Mac, instead of a Windows machine. I'm using the Azure CLI for authenticating, and on this Mac, I have an additional subscription logged in the Azure CLI. I suspect that triggered an error in Terraform.

@ghost
Copy link

ghost commented Jun 20, 2019

This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#3706 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-azurerm#3706.

@ghost ghost closed this as completed Jun 20, 2019
@ghost
Copy link

ghost commented Jul 25, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jul 25, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants