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

Trying to create an Express Route Gateway getting SKU error #349

Closed
jceval opened this issue Nov 3, 2021 · 2 comments · Fixed by #350
Closed

Trying to create an Express Route Gateway getting SKU error #349

jceval opened this issue Nov 3, 2021 · 2 comments · Fixed by #350
Milestone

Comments

@jceval
Copy link
Contributor

jceval commented Nov 3, 2021

Passing the following parameters to the module and receiving an error related to the SKU used.

module networkEGW '../../../arm/Microsoft.Network/virtualNetworkGateways/deploy.bicep' = if (networkObject.peeredToHub==false) {
  name: 'networkEGW-${location}-${env}-${nameSuffix}'
  scope: resourceGroup(networkObject.subscriptionId, resourceGroupName)
  params: {
    virtualNetworkGatewayName: 'egw-${location}-${env}-${nameSuffix}'
    virtualNetworkGatewayType: 'ExpressRoute'
    virtualNetworkGatewaySku: 'ErGw1AZ'
    vNetId: networkVNET.outputs.virtualNetworkResourceId
    activeActive: false
    publicIpZones: []
  }

  dependsOn: [
    networkRG
    networkVNET
  ]
}

Error : The deployed SKU is in the allowed SKU list in the error. Resource should be deploying with Standard Static PIP and Express Route Gateway Type , ErGw1AZ SKU , and no availability zone configuration since not available in canada east.

{
    "status": "Failed",
    "error": {
        "code": "InvalidGatewaySkuSpecifiedForGatewayDeploymentType",
        "message": "Virtual network gateway Sku specified is not valid for gateway /subscriptions/<sub_id>/resourceGroups/rg-network-canadaeast-prod-connectivity/providers/Microsoft.Network/virtualNetworkGateways/egw-canadaeast-prod-connectivity with DeploymentType VMScaleSet. The allowed Skus are ErGw1AZ,ErGw2AZ,ErGw3AZ.",
        "details": []
    }
}
@jceval
Copy link
Contributor Author

jceval commented Nov 3, 2021

Similar to this thread : hashicorp/terraform-provider-azurerm#9892

@ahmadabdalla ahmadabdalla linked a pull request Nov 3, 2021 that will close this issue
7 tasks
@ahmadabdalla
Copy link
Contributor

@jceval For Canada East, as it doesn't support AZs yet, the parameters should deploy using either the (Standard, HighPerformance, UltraPerformance) SKUs. I've added them to the allowed list and this will convert the PIP to Basic and Dynamic as well.

@rahalan rahalan added this to the Public Preview milestone Nov 3, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants