New-AzureRmVmss show incorect message HealthProbe resource missing

[DanielHWe]

Description

I create first a Network Load Balancer include HealthProbe etc. and then on create the according Vm Scale Set with New-AzureRmVmss, I got the message that the HealthProbe is missing. But by checking on the azure portel the HealthProbe was correctly create within the Load Balancer resource.

Script/Steps for Reproduction

# Set required Variables
$lbName = "NRP-LB"
$loc = "<My Region>"
$currentrg = "<My rg name>"
$vnetname = "<My Vnet Name>"
$vnetrg = "<Name of RG conteining my vnet>"

$vmPassword = ConvertTo-SecureString $adminPassword -AsPlainText -Force
$vmCred = New-Object System.Management.Automation.PSCredential($adminUsername, $vmPassword)

# Set Network
$vnet= Get-AzureRmVirtualNetwork -Name $vnetname -ResourceGroupName $vnetrg
$subnetMain = $vnet.Subnets[2]
$backendSubnetName = $subnetMain.Name


#Deploy Loadbalancer
$frontendIP = New-AzureRmLoadBalancerFrontendIpConfig `
     -Name LB-Frontend `
     -SubnetId $subnetMain.Id `
     -ErrorAction Stop 

$beaddresspool= New-AzureRmLoadBalancerBackendAddressPoolConfig `
     -Name "LB-backend" `
     -ErrorAction Stop

$inboundNATRule1= New-AzureRmLoadBalancerInboundNatRuleConfig `
     -Name "RDP" `
     -FrontendIpConfiguration $frontendIP `
     -Protocol TCP `
     -FrontendPort 3389 `
     -BackendPort 3389 `
     -ErrorAction Stop

$healthProbe = New-AzureRmLoadBalancerProbeConfig `
     -Name "HealthProbe" `
     -RequestPath "Default.htm" `
     -Protocol http `
     -Port 80 `
     -IntervalInSeconds 15 `
     -ProbeCount 2 `
     -ErrorAction Stop

$lbrule = New-AzureRmLoadBalancerRuleConfig `
     -Name "HTTP" `
     -FrontendIpConfiguration $frontendIP `
     -BackendAddressPool $beAddressPool `
     -Probe $healthProbe `
     -Protocol Tcp `
     -FrontendPort 80 `
     -BackendPort 80

$nrplb = New-AzureRmLoadBalancer `
     -ResourceGroupName $currentrg `
     -Name $lbName `
     -Location $loc `
     -FrontendIpConfiguration $frontendIP `
     -InboundNatRule $inboundNATRule1 `
     -LoadBalancingRule $lbrule `
     -BackendAddressPool $beAddressPool `
     -Probe $healthProbe 

#Deploy VM Scale Set ==> Error
New-AzureRmVmss `
  -Credential $vmCred `
  -ResourceGroupName $currentrg `
  -Location $loc `
  -VMScaleSetName $vmssName `
  -PublicIpAddressName $frontendIP.Name `
  -LoadBalancerName  $lbName `
  -UpgradePolicy "Automatic" `
  -ErrorAction Stop `
  -VirtualNetworkName $vnetname `
  -SubnetName $backendSubnetName `

Module Version

6.2.1

Environment Data

Name Value

---

PSVersion 5.1.16299.431
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.16299.431
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Debug Output

WARNUNG: The output object type of this cmdlet will be modified in a future release.

New-AzureRmVmss : Resource /subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Network/loadBal
ancers/NRP-LB/loadBalancingRules/HTTP referenced by resource /subscriptions/XXX/resourceGroups/XXX/p
roviders/Microsoft.Network/loadBalancers/NRP-LB/probes/HealthProbe was not found. Please make sure that the referenced resource exists, and 
that both resources are in the same region.
In D:\scripts\create_loadBalancer_and_vmss.ps1:228 Zeichen:1
+ New-AzureRmVmss `
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzureRmVmss], CloudException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Compute.Automation.NewAzureRmVmss

[markcowl]

@praries880 @hyonholee Can you take a look?

[praries880]

@DanielHWe I have a local repro as well.

@hyonholee
Here are the steps i ran :

$publicip = New-AzureRmPublicIpAddress -ResourceGroupName "parytest1" -Name "MyPublicIp" -Location "East US" -AllocationMethod "Dynamic"
$frontend = New-AzureRmLoadBalancerFrontendIpConfig -Name "MyFrontEnd" -PublicIpAddress $publicip
$backendAddressPool = New-AzureRmLoadBalancerBackendAddressPoolConfig -Name "MyBackendAddPoolConfig02"
$probe = New-AzureRmLoadBalancerProbeConfig -Name "MyProbe" -Protocol "http" -Port 80 -IntervalInSeconds 15 -ProbeCount 2 -RequestPath "healthcheck.aspx"
$inboundNatRule1 = New-AzureRmLoadBalancerInboundNatRuleConfig -Name "MyinboundNatRule1" -FrontendIPConfiguration $frontend -Protocol "Tcp" -FrontendPort 3389 -BackendPort 3389 -IdleTimeoutInMinutes 15 -EnableFloatingIP
$inboundNatRule2 = New-AzureRmLoadBalancerInboundNatRuleConfig -Name "MyinboundNatRule2" -FrontendIPConfiguration $frontend -Protocol "Tcp" -FrontendPort 3391 -BackendPort 3392
$lbrule = New-AzureRmLoadBalancerRuleConfig -Name "MyLBruleName" -FrontendIPConfiguration $frontend -BackendAddressPool $backendAddressPool -Probe $probe -Protocol "Tcp" -FrontendPort 80 -BackendPort 80 -IdleTimeoutInMinutes 15 -EnableFloatingIP -LoadDistribution SourceIP
$lb = New-AzureRmLoadBalancer -Name "MyLoadBalancer" -ResourceGroupName "parytest1" -Location "East US" -FrontendIpConfiguration $frontend -BackendAddressPool $backendAddressPool -Probe $probe -InboundNatRule $inboundNatRule1,$inboundNatRule2 -LoadBalancingRule $lbrule

New-AzureRmVmss  -ResourceGroupName parytest1   -Location "East US"   -VMScaleSetName "paryvmss1"
 -PublicIpAddressName $frontendIP.Name   -LoadBalancerName  "MyLoadBalancer"   -UpgradePolicy "Automatic"   -ErrorAction
 Stop

cmdlet New-AzureRmVmss at command pipeline position 1
Supply values for the following parameters:
Credential
New-AzureRmVmss : Resource /subscriptions/<redacted>/resourceGroups/parytest1/providers/Micro
soft.Network/loadBalancers/MyLoadBalancer/loadBalancingRules/MyLBruleName referenced by resource /subscriptions/<redacted>/resourceGroups/parytest1/providers/Microsoft.Network/loadBalancers/MyLoadBalancer/probes/
MyProbe was not found. Please make sure that the referenced resource exists, and that both resources are in the same
region.
At line:1 char:1
+ New-AzureRmVmss  -ResourceGroupName parytest1   -Location "East US"   ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzureRmVmss], CloudException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Compute.Automation.NewAzureRmVmss

The LB Rule does exist, as can be seen here:

$lb = Get-AzureRmLoadBalancer -Name "MyLoadBalancer" -ResourceGroupName "parytest1"

PS C:\Users\paresin> $lb | select Name, ResourceGroupName

Name           ResourceGroupName
----           -----------------
MyLoadBalancer parytest1


PS C:\Users\paresin> $lb.Probes | select Name, RequestPath, LoadBalancingRules

Name    RequestPath      LoadBalancingRules
----    -----------      ------------------
MyProbe healthcheck.aspx {/subscriptions/<redacted>/resourceGroups/parytest1/providers/Mic...


PS C:\Users\paresin> $lb.LoadBalancingRules | select Name, ProvisioningState

Name         ProvisioningState
----         -----------------
MyLBruleName Succeeded

The error seems to be coming from the service itself :

RequestId      : 303c2d29-f001-4bf4-8ab1-c6bf9dd89672
Message        : Resource /subscriptions/<redacted>/resourceGroups/parytest1/providers/Micros
                 oft.Network/loadBalancers/MyLoadBalancer/loadBalancingRules/MyLBruleName referenced by resource /subsc
                 riptions/<redacted>/resourceGroups/parytest1/providers/Microsoft.Network/loa
                 dBalancers/MyLoadBalancer/probes/MyProbe was not found. Please make sure that the referenced resource
                 exists, and that both resources are in the same region.
ServerMessage  : InvalidResourceReference: Resource /subscriptions/<redacted>/resourceGroups/
                 parytest1/providers/Microsoft.Network/loadBalancers/MyLoadBalancer/loadBalancingRules/MyLBruleName
                 referenced by resource /subscriptions/<redacted>/resourceGroups/parytest1/pr
                 oviders/Microsoft.Network/loadBalancers/MyLoadBalancer/probes/MyProbe was not found. Please make sure
                 that the referenced resource exists, and that both resources are in the same region.
                 (System.Collections.Generic.List`1[Microsoft.Rest.Azure.CloudError])
ServerResponse : {BadRequest}
RequestMessage : {PUT https://management.azure.com/subscriptions/<redacted>/resourceGroups/pa
                 rytest1/providers/Microsoft.Network/loadBalancers/MyLoadBalancer?api-version=2017-10-01}
InvocationInfo : {New-AzureRmVmss}
Line           : New-AzureRmVmss  -ResourceGroupName parytest1   -Location "East US"   -VMScaleSetName "paryvmss1"
                 -PublicIpAddressName $frontendIP.Name   -LoadBalancerName  "MyLoadBalancer"   -UpgradePolicy
                 "Automatic"   -ErrorAction Stop
Position       : At line:1 char:1
                 + New-AzureRmVmss  -ResourceGroupName parytest1   -Location "East US"   ...
                 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
StackTrace     :    at Microsoft.Azure.Commands.Common.Strategies.SyncTaskScheduler.Wait(Task task, Action
                 progressUpdate)
                    at Microsoft.Azure.Commands.Compute.Automation.NewAzureRmVmss.ExecuteCmdlet()
                    at Microsoft.WindowsAzure.Commands.Utilities.Common.AzurePSCmdlet.ProcessRecord()
HistoryId      : 16