Error destroying resource that has already been deleted.

[clstokes]

If an azurerm_storage_account resource has already been removed, Terraform is unable to proceed with a destroy due to a 404 error.

Steps to Reproduce

1. Perform terraform apply with configuration below.
2. Delete the storage account from the Azure portal.
3. Run a terraform destroy

Example Config

resource "azurerm_storage_account" "test" {
  name                = "teststorageaccount2016"
  resource_group_name = "${azurerm_resource_group.test.name}"
  location            = "westus"
  account_type        = "Standard_LRS"

  tags {
    environment = "staging"
  }
}

Error log

terraform $ terraform destroy
Do you really want to destroy?
  Terraform will delete all your managed infrastructure.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

azurerm_resource_group.test: Refreshing state... (ID: /subscriptions/XYZ/resourceGroups/acctestrg)
azurerm_storage_account.test: Refreshing state... (ID: /subscriptions/XYZ/resourceGroups/acctestrg/providers/Microsoft.Storage/storageAccounts/hashicorpaccsa)
azurerm_virtual_network.test: Refreshing state... (ID: /subscriptions/XYZ/resourceGroups/acctestrg/providers/Microsoft.Network/virtualNetworks/acctvn)
azurerm_subnet.test: Refreshing state... (ID: /subscriptions/XYZ/resourceGroups/acctestrg/providers/Microsoft.Network/virtualNetworks/acctvn/subnets/acctsub)
azurerm_network_interface.test: Refreshing state... (ID: /subscriptions/XYZ/resourceGroups/acctestrg/providers/Microsoft.Network/networkInterfaces/acctni)
Error refreshing state: 1 error(s) occurred:

* azurerm_storage_account.test: Error reading the state of AzureRM Storage Account "hashicorpaccsa": autorest:DoErrorUnlessStatusCode 404 GET https://management.azure.com/subscriptions/XYZ/resourceGroups/acctestrg/providers/Microsoft.Storage/storageAccounts/hashicorpaccsa?api-version=2015-06-15 failed with 404 Not Found
terraform $

[clstokes]

Similar to #3990 - Terraform destroy does not handle 404 on Google Compute Instance.

[stack72]

Hi @clstokes

Am just preparing a fix for this right now :) good find on this

P.

[jen20]

@clstokes This fix is now on master.

[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 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.