Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Regions with out support for 3 fault domains fail to provision #9

Open
davidsandilands opened this issue Aug 3, 2022 · 0 comments
Open
Labels
bug Something isn't working jira

Comments

@davidsandilands
Copy link
Member

Describe the Bug

When attempting to provision on to regions with only compatibility for 2 fault domains in an availability region provisioning will fail as the terraform defaults to 3.

Expected Behavior

We would expect the module to use 3 if available and fail to 2 otherwise

Steps to Reproduce

Provisioning a large or xlarge setup to a region like UKSOUTH

Failed on localhost:

Error: compute.AvailabilitySetsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidParameter" Message="The specified fault domain count 3 must fall in the range 1 to 2." Target="platformFaultDomainCount"

    with module.instances.azurerm_availability_set.compiler_availability_set[0],
    on modules\instances\main.tf line 184, in resource "azurerm_availability_set" "compiler_availability_set":
   184: resource "azurerm_availability_set" "compiler_availability_set" {

Failed on 1 target: localhost
Ran on 1 target

Additional Context

(https://github.com/MicrosoftDocs/azure-docs/blob/main/includes/managed-disks-common-fault-domain-region-list.md)

@davidsandilands davidsandilands added the bug Something isn't working label Aug 3, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working jira
Projects
None yet
Development

No branches or pull requests

1 participant