Error on Terraform Apply: CosmosDB account name already exists

[khaljimbo]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.12.3

• provider.azurerm v1.31.0

Affected Resource(s)

azurerm_cosmosdb_account

Terraform Configuration Files

resource "azurerm_cosmosdb_account" "db" {
  name                = "${var.cosmosDBAccountName}"
  location            = "${var.location}"
  resource_group_name = "${var.resourceGroupName}"
  offer_type          = "Standard"
  kind                = "GlobalDocumentDB"

  enable_automatic_failover = true

  consistency_policy {
    consistency_level       = "Session"
  }

  geo_location {
    location          = "${var.failoverLocation}"
    failover_priority = 1
  }

  geo_location {
    prefix            = "${var.cosmosDBAccountName}"
    location          = "${var.location}"
    failover_priority = 0
  }
}

Expected Behavior

CosmosDB account should be created

Actual Behavior

Error: CosmosDB Account 1239website0918627public already exists, please import the resource via terraform import

on cosmosDBwithMongoDBAPI.tf line 6, in resource "azurerm_cosmosdb_account" "db":
6: resource "azurerm_cosmosdb_account" "db" {

Steps to Reproduce

Use simple terraform to create a cosmos DB account. No matter how many random characters are used to create a CosmosDB account it complains that the name already exists.

1. terraform apply

References

I found issue #3739 which suggests this is fixed in version 1.31 of the azure provider but I am still seeing this error.

[centran]

I want to add that the error reported occurs the second time you run terraform apply. The first time you get an error like this:

Error: Error creating CosmosDB Account "#####" (Resource Group "#####"): Error creating/updating CosmosDB Account "#####" (Resource Group "#####"): documentdb.DatabaseAccountsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="DatabaseAccount name '#####' already exists.\r\nActivityId: #####, Microsoft.Azure.Documents.Common/2.5.1"

Then if you run terraform apply you get the error orginally report about importing the resource. Checking the Azure portal, CLI, and API calls does not show the name anywhere.

I'm not sure this is a terraform issue. It seems that the Azure API starts to create the cosmosDB account, reserves the name, then fails. After that the name is reserved but not attached to your Azure subscription so you can't recover the name. You can't even try to use the name through the portal after it fails in terraform.

Maybe there is a bug with how the azurerm terraform provider calls the Azure API but I also feel Azure should not allow this behavior. There is probably a DoS exploit which can be carried out with this bug.

[dhsass]

We're getting this error on the first attempt to create the db. We even tried using a GUID as the name and got this error.

[jnunham]

@dhsass @khaljimbo Several people at my company have run in to this and discovered that if you reuse the account name for the geo_location prefix, this is what is causing the issue. 2 solutions to this:

#1. Remove the prefix altogether (this will just make the Azure API auto generate one for you)

#2. Follow the updated method on the Terraform documentation page, particularly:
prefix = "tfex-cosmos-db-${random_integer.ri.result}-customid"

Hope this fixes it for you!

[DaSenf]

I still get the same errors all the time.
I tried all kind of "hello world"-configurations and location variations.

But whenever i only use one location, it says there is nothing available although i use one which is "recommened" in the Azure portal

when i use a failover location it says: Code="BadRequest" Message="Cannot add additional regions, since database account provision failed

[DaSenf]

I´m stupid i used location names (like East Us) instead of location ids (like eastus) ...

[tombuildsstuff]

👋

Taking a look through I believe @jnunham's comment above should resolve this - as such I'm going to close this issue for the moment

Thanks!

[ghost]

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 👉 hashibot-feedback@hashicorp.com. Thanks!