Comment 0 for bug 1824465

Hi,

We recently upgraded one of our cloud archive mirrors in Azure to Juju 2.5.4. Unfortunately, this now breaks provisioning of new units because the load balancer "SKU" Juju provisions with has changed from "Basic" to "Standard".

The Azure portal for instances failing provisioning shows the following:

| Additional error information is available for this virtual machine:
| GENERAL
| Provisioning state Provisioning failed. Different basic sku and standard sku load balancer or public Ip resources in availability set is not allowed /subscriptions/bb7e37e8-bc53-403a-a4a9-4dd507d7813b/resourceGroups/juju-archive-mirror-azure-central-us-model-417ca9a1-d880-4c09-885a-8a0e6ee57ee3/providers/Microsoft.Network/publicIPAddresses/machine-0-public-ip and /subscriptions/bb7e37e8-bc53-403a-a4a9-4dd507d7813b/resourceGroups/juju-archive-mirror-azure-central-us-model-417ca9a1-d880-4c09-885a-8a0e6ee57ee3/providers/Microsoft.Network/publicIPAddresses/machine-6-public-ip.. DifferentSkuLoadBalancersAndPublicIPAddressNotAllowed
| Provisioning state error code ProvisioningState/failed/DifferentSkuLoadBalancersAndPublicIPAddressNotAllowed
| Guest agent Not Ready. VM status blob is found but not yet populated.
| DISKS
| machine-6 Provisioning succeeded.

For these environments, they were deployed pre-Juju 2.5.x and therefore using the "basic SKU".

It might be https://github.com/juju/juju/pull/9499 and commit '9cd72eb26a07e4f662caa5d9f89cae4fedabbfb7' switching to "standard".

I think we should detect what was previously used and provision units using matching SKUs. I think we should also provide the ability to override the SKU for those wishing to use either "basic" or "standard".

FWIW, standard was originally requested in LP: #1799238 because it seems to be the one that provides network metrics.