azurerm_availability_set missing a force recreate

[cchildress]

Terraform Version

0.7.13

Affected Resource(s)

• azurerm_availability_set

Terraform Configuration Files

Before:

resource "azurerm_availability_set" "foobar" {
  name                         = "foobar"
  location                     = "westeurope"
  resource_group_name          = "${azurerm_resource_group.rg.name}"
  platform_fault_domain_count  = "2"
  platform_update_domain_count = "3"
}

After:

resource "azurerm_availability_set" "foobar" {
  name                         = "foobar"
  location                     = "westeurope"
  resource_group_name          = "${azurerm_resource_group.rg.name}"
  platform_fault_domain_count  = "3"
  platform_update_domain_count = "5"
}

Debug Output

15:09:14 * azurerm_availability_set.foobar: compute.AvailabilitySetsClient#CreateOrUpdate: Failure responding to request: StatusCode=409 -- Original Error: autorest/azure: Service returned an error. Status=409 Code="PropertyChangeNotAllowed" Message="Changing property 'platformFaultDomainCount' is not allowed."
15:09:14 * azurerm_availability_set.foobar: compute.AvailabilitySetsClient#CreateOrUpdate: Failure responding to request: StatusCode=409 -- Original Error: autorest/azure: Service returned an error. Status=409 Code="PropertyChangeNotAllowed" Message="Changing property 'platformFaultDomainCount' is not allowed."

Expected Behavior

Terraform should force a resource recreate for the availability set if the fault domain count is altered.

Actual Behavior

Terraform attempts to change the fault domain count in Azure, but Azure returns a failure code.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Create an availability set with n fault domains.
2. Alter the availability set to add to the number of fault domains.
3. Run terraform apply and it should fail to alter the AS.

[stack72]

Closed via #10545

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