You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
locked and limited conversation to collaborators
Mar 28, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
1.39
Affected Resource(s)
azurerm_container_group
Terraform Configuration Files
Debug Output
Panic Output
crash.log
Expected Behavior
execute terraform apply twice, it works fine.
Actual Behavior
execute terraform apply twice, it will panic.
Steps to Reproduce
terraform apply -auto-approve -var 'client_id=$(ARM_CLIENT_ID)' -var 'subscription_id=$(ARM_SUBSCRIPTION_ID)' -var 'client_secret=$(ARM_CLIENT_SECRET)' -var 'tenant_id=$(ARM_TENANT_ID)' -var 'jmeter_docker_image=$(image_name)'
execute the same terraform apply as 1. -> panic
Important Factoids
no
References
The root cause might be this line. According to the log, the response doesn't include IPAddress on property.
https://github.com/terraform-providers/terraform-provider-azurerm/blob/master/azurerm/internal/services/containers/resource_arm_container_group.go#L581
The text was updated successfully, but these errors were encountered: