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) #3706

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

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

ghost opened this issue Jun 20, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Jun 20, 2019

This issue was originally opened by @tiesmaster as hashicorp/terraform#21816. It was migrated here as a result of the provider split. The original body of the issue is below.


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.

@mbfrahry
Copy link
Member

Hey @tiesmaster. This seems to be related to #3657 which has been merged and should go out with the next release. I'm going to close this issue down but feel free to reopen this if you continue to experience this after the next release.

@ghost
Copy link
Author

ghost commented Jul 21, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

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

No branches or pull requests

1 participant