[AVM Module Issue]: Load balancer module not adding backend pool vms and also not giving any error

[abhiramani-git]

Check for previous/existing GitHub issues

• [X] I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/network/load-balancer

(Optional) Module Version

0.3.0

Description

Load balancer backendpools not adding the 2 vms i specify in my backend pool parameter file. below are my bicep and bicep param file

param lbName string
param frontendIPConfigurations array
param backendAddressPools array
param probes array
param loadBalancingRules array

module mylb 'br/public:avm/res/network/load-balancer:0.3.0' = {
  name: 'mydemo'
  params: {
    name: lbName
    frontendIPConfigurations: frontendIPConfigurations
    backendAddressPools: backendAddressPools
    probes: probes
    loadBalancingRules: loadBalancingRules
  }
}

using '../internalLb.bicep'
param lbName='mylbpoc'
param frontendIPConfigurations = [
      {
        name: 'sql-frontend'
        subnetId: '/subscriptions/<replace wih SubId>/resourceGroups/<replace with rg>/providers/Microsoft.Network/virtualNetworks/linux-sandbox-01VNET/subnets/agwsubnet'
        // privateIPAddress:'10.0.1.4'
        zones:[
              '1'
              '2'
              '3'
            ]

      }
      {
        name: 'wsfc-frontend'
        subnetId: '/subscriptions/<replace wih SubId>/resourceGroups/<replace with rg>/providers/Microsoft.Network/virtualNetworks/linux-sandbox-01VNET/subnets/agwsubnet'
        // privateIPAddress:'10.0.1.5'
        zones:[
              '1'
              '2'
              '3'
            ]
      }
    ]

param backendAddressPools = [
    {
        name: 'backendAddressPool1'
        properties: {
            loadBalancerBackendAddresses: [
                {
                    name: 'linux-sandbox-01'
                    properties: {
                         virtualNetwork: {
                             id: '/subscriptions/<replace wih SubId>/resourceGroups/<replace with rg>/providers/Microsoft.Network/virtualNetworks/linux-sandbox-01VNET'
                         }
                        ipAddress: '10.0.0.4'
                    }
                }
                {
                    name: 'linux-sandbox-02'
                    properties: {
                         virtualNetwork: {
                             id: '/subscriptions/<replace wih SubId>/resourceGroups/<replace with rg>/providers/Microsoft.Network/virtualNetworks/linux-sandbox-01VNET'
                         }
                        ipAddress: '10.0.0.10'
                    }
                }
            ]
        }
    }
]
param probes =  [
      {
        name: 'sql-probe'
        port: 5999
        protocol: 'tcp'
        intervalInSeconds: 5
        numberOfProbes: 1

      }
      {
        name: 'wsfc-probe'
        port: 5888
        protocol: 'tcp'
        intervalInSeconds: 5
        numberOfProbes: 1

      }

    ]

param loadBalancingRules = [
      {
        name: 'sql-lbRule'
        backendAddressPoolName: 'backendAddressPool1'
        backendPort: 5999
        frontendIPConfigurationName: 'sql-frontend'
        frontendPort: 5999
        idleTimeoutInMinutes: 4
        probeName: 'sql-probe'
        protocol: 'Tcp'
      }
      {
        name: 'wsfc-lbRule'
        backendAddressPoolName: 'backendAddressPool1'
        backendPort: 5888
        frontendIPConfigurationName: 'wsfc-frontend'
        frontendPort: 5888
        idleTimeoutInMinutes: 4
        probeName: 'wsfc-probe'
        protocol: 'Tcp'
      }
    ]

(Optional) Correlation Id

No response

[microsoft-github-policy-service[bot]]

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter[bot]]

@abhiramani-git, thanks for submitting this issue for the avm/res/network/load-balancer module!

[!IMPORTANT] A member of the @Azure/avm-res-network-loadbalancer-module-owners-bicep or @Azure/avm-res-network-loadbalancer-module-contributors-bicep team will review it soon!

[microsoft-github-policy-service[bot]]

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!

[microsoft-github-policy-service[bot]]

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!