Operational Defect Database
BugZero found this defect 1435 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000booWSAQ
Firebox Cloud fails to deploy in Azure when the deployment uses an existing Vnet that is also used by a VM scale set
Last update date:
6/24/2020
Affected products:
Firebox Cloud
Affected releases:
All
Fireware
12.x
12.5.x
Fixed releases:
All
Description:
Issue
When you deploy Firebox Cloud to Azure, if you select a virtual network (Vnet) that is used by a scale set for one of the Firebox Cloud interfaces, the deployment can fail if the Firebox gets an IP address that is used by a running or stopped scale set instance. When the deployment fails, you see this error message: IP configuration /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/Firebox-Cloud-RG/providers/Microsoft.Network/networkInterfaces/fireboxcloudEth1/ipConfigurations/ipconfig1 is using the private IP address 10.1.5.4 which is already allocated to resource /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/Scale-Set-RG/providers/Microsoft.Network/networkInterfaces/|providers|Microsoft.Compute|virtualMachineScaleSets|ubuntu-scale-set-vm|virtualMachines|0|networkInterfaces|Scale-Set-RG-vnet-nic01
Workaround/Solution
Add another scale set instance, delete the scale set instance that uses the IP address referenced in the error message, and then try to deploy Firebox Cloud again.
