You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AzureBasicLoadBalancerUpgrade/module/AzureBasicLoadBalancerUpgrade/modules/ValidateScenario/ValidateScenario.psm1
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -664,7 +664,7 @@ Function Test-SupportedMigrationScenario {
$message="[Test-SupportedMigrationScenario] VMs ('$($extraAvailabilitySetVMs-join';')') belong(s) to an Availability Set and there are other members of the same Availability Set which are part of the load balancer backend pools, NAT pools, or associated with NAT Rules. This is not supported for migration. To work around this, create a new backend pool on the basic LB which is not associated with a load balancing rule and add the extra VMs to it temporarily, then retry migration."
667
+
$message="[Test-SupportedMigrationScenario] VMs ('$($extraAvailabilitySetVMs-join';')') belong(s) to an Availability Set but is not associated with the LB. There are other members of the same Availability Set which are part of the load balancer backend pools, NAT pools, or associated with NAT Rules. This is not supported for migration. To work around this, create a new backend pool on the basic LB which is not associated with a load balancing rule and add the extra VMs to it temporarily, then retry migration."
@@ -832,11 +832,12 @@ Function Test-SupportedMultiLBScenario {
832
832
}
833
833
834
834
# VMs must share an availability set or the backend must be a single VM with no availability set ('NO_AVAILABILITY_SET')
835
-
If (($VMAvailabilitySets.availabilitySetId|Sort-Object|Get-Unique).count -gt1-or ($VMAvailabilitySets.availabilitySetId|Where-Object { $_-eq'NO_AVAILABILITY_SET' }).count -gt1) {
836
-
log -Severity Error -Message "[Test-SupportedMultiLBScenario] The provided Basic Load Balancers do not share backend pool members (VMs are in different or no Availability Sets: '$($VMAvailabilitySets.availabilitySetId-join',')'). Using -multiLBConfig when backend is not shared adds risk and complexity in recovery."-terminateOnError
If (($uniqueAvailabilitySets.count-gt1-or ($VMAvailabilitySets.availabilitySetId|Where-Object { $_-eq'NO_AVAILABILITY_SET' }).count -gt1)) {
837
+
log -Severity Error -Message "[Test-SupportedMultiLBScenario] The provided Basic Load Balancers do not share backend pool members (VMs are in different or no Availability Sets: '$($uniqueAvailabilitySets-join',')'). Using -multiLBConfig when backend is not shared adds risk and complexity in recovery."-terminateOnError
0 commit comments