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
When creating VMs, and the original count is 1, then only 1 VM is created. However, if later it's decided you want 2+ of that VM, and you set the count to say 3, then 2 more VMs are created, with a new Availability Set and Load Balancer; yet only the latter 2 are added to the AS/LB.
This issue is to fix a bug, so that the former first VM is also added into the AS/LB.
The text was updated successfully, but these errors were encountered:
Unfortunately due to a massive design flaw on Microsoft's part, you cannot a an already created VM into an newly created Availability Set...
Therefore, until this issue is resolved on their end, I've set it so that an AS is always created - even for one VM. At least this way you can increase the VM count without worrying too much.
I will at some point look into the removing of VMs for when you lower the count value.
When creating VMs, and the original count is 1, then only 1 VM is created. However, if later it's decided you want 2+ of that VM, and you set the count to say 3, then 2 more VMs are created, with a new Availability Set and Load Balancer; yet only the latter 2 are added to the AS/LB.
This issue is to fix a bug, so that the former first VM is also added into the AS/LB.
The text was updated successfully, but these errors were encountered: