Open TravBricks opened 8 months ago
Thanks for opening this issue. You've listed that this is an issue in the 2.x version of the provider which is no longer actively maintained. If you are able to upgrade and this is still an issue with the 3.x version of the provider please do let us know and we can reopen this issue.
My bad, same thing happened with v3.93.0
Error:
Error: creating/updating Workspace (Subscription: "[redact]"
│ Resource Group Name: "terraform_travislongwell-rg"
│ Workspace Name: "[redact]"): polling after CreateOrUpdate: polling failed: the Azure API returned the following error:
│
│ Status: "ApplianceProvisioningFailed"
│ Code: ""
│ Message: "The managed resource group '/subscriptions/[redact]/resourceGroups/databricks-rg-terraform-rg' already exists. Please specify a new non-existent managed resource group"
│ Activity Id: ""
│
│ ---
│
│ API Response:
│
│ ----[start]----
│ {
│ "status": "Failed",
│ "error": {
│ "code": "ApplianceProvisioningFailed",
│ "message": "The managed resource group '/subscriptions/[redact]/resourceGroups/databricks-rg-terraform-rg' already exists. Please specify a new non-existent managed resource group"
│ }
│ }
│ -----[end]-----
│
│
│ with module.workspace_2.azurerm_databricks_workspace.this,
│ on modules/databricks_workspace/workspace.tf line 1, in resource "azurerm_databricks_workspace" "this":
│ 1: resource "azurerm_databricks_workspace" "this" {
│
TF version and azurerm provider version:
Terraform v1.5.7
on darwin_arm64
+ provider registry.terraform.io/hashicorp/azurerm v3.93.0
I updated to v3.9.3 and confirmed that it provides more feedback about the error, but still behaves incorrectly.
On Thu, Feb 29, 2024 at 12:33 PM Renae Kosir @.***> wrote:
Thanks for opening this issue. You've listed that this is an issue in the 2.x version of the provider which is no longer actively maintained. If you are able to upgrade and this is still an issue with the 3.x version of the provider please do let us know and we can reopen this issue.
— Reply to this email directly, view it on GitHub https://github.com/hashicorp/terraform-provider-azurerm/issues/25090#issuecomment-1971627707, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZD3YSGOZGD3QIQGORAJP6DYV5S6LAVCNFSM6AAAAABD66FYR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRGYZDONZQG4 . You are receiving this because you authored the thread.Message ID: @.***>
@TravBricks Thank you for the additional information, reopening!
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
2.99.0
Affected Resource(s)/Data Source(s)
azurerm_databricks_workspace
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
When the optional
managed_resource_group_name
is not included a unique MRG name should be generated and used by the workspace.Actual Behaviour
There is a
managed_resource_group_name
reused for both workspaces resulting in a failed deployment for the second workspace.Steps to Reproduce
Important Factoids
No response
References
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/databricks_workspace#managed_resource_group_name