Terraform: creating azurerm storage account fails (from timeout) first time

Created on 17 May 2016 · 9Comments · Source: hashicorp/terraform

when doing a terraform apply with a azurerm_storage_account

it will spend like 10 minutes trying to create it and then fail. but when you runn apply again it will work almost immediately.

this should be a fairly quick operation.

bug provideazurerm

Source

MattFenner

Most helpful comment

I too see this on a regular basis. I don't see any notifications other than that terraform keeps tracking the progress. This is on terraform 0.9.5. Can we please re-open this bug. I consistently hit this issue wherein the storage account does not get created for a long time. I always have to kill terraform and then retry again and hope it works.

vinayvenkat on 6 Jul 2017

👍4

All 9 comments

Hi @MattFenner - is this something that is repeatable in your Azure account? If so would you be prepared to undertake some additional debugging research for us? I have not seen this in any of our test accounts, though the time taken does vary from seconds to multiple minutes.

jen20 on 17 May 2016

it is consistently about 15min for me. assuming it is pretty easy to do i can get some debug info for you

MattFenner on 17 May 2016

Hey, @MattFenner , try changing the name of the storage account every time. There is an issue with azure. It holds the storage account name even after it is destroyed for couple of hours.

ManushB on 17 May 2016

Hi @MattFenner

The information that @ManushB gave is indeed correct. StorageAccount names are unique across the entire of AzureRM so you will not be able to destroy and recreate in quick succession

Paul

stack72 on 17 May 2016

👍2

+1 to above. I've found that after destroying a storage account, you usually need to wait about 15 minutes for that name to be reusable.

Preskton on 18 May 2016

Hi folks

We believe we have made this experience better in #8215 where we are much better about interacting with long running processes

I am going to close this for now - if this happens again then please let us know

Paul

stack72 on 18 Aug 2016

vinayvenkat on 6 Jul 2017

👍4

This issue still exist. I have reproduced this on terraform 0.10.2.

bernadinm on 30 Aug 2017

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.