search

F5Networks / f5-azure-arm-templates-v2

Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
22 stars 45 forks source link

Failover always be deployed into AvailabilityZone 1 #18

Closed TomTomDE closed 2 years ago

TomTomDE commented 2 years ago

Describe the bug

If we deploy Failover Template, with or without Existing Stack. Both Failover Instances are deployed into Availability Zone 1 if useAvailabilityZones is set to true (bool)

Expected behavior

if useAvailabilityZones is set to true Availability Zones should be used and the 2 virtual Machines should be stretched accross multiple Zones like 1 and 2, 2 and 3 or 1 and 3

Current behavior

if useAvailabilityZones is set to true, both VMs deployed on Availability Zone 1

Possible solution / problem location

Code-Line in examples/modules/bigip-standalone/bigip.json "zones": "[if(parameters('useAvailabilityZones'), createArray(1), json('null'))]", createArray(1) << this set the used Zone always to 1

Idea

let Zones be defined in ARM Template Deployment as Variable ... like Zone VM1 = 1, Zone VM2 = 2

mikeshimkus commented 2 years ago

Hi @TomTomDE, thanks for reporting. This was fixed with internal issue #3136, which will be included in the next release.

TomTomDE commented 2 years ago

thanks, working

shyawnkarim commented 2 years ago

Closing.

This issue was resolved with Release 2.4.0.0.