Bootstrap azure with juju 2.9.29:
-----
$ juju bootstrap azure/centralus arc-ubu --model-default 'logging-config=<root>=DEBUG'
Creating Juju controller "arc-ubu" on azure/centralus
Looking for packaged Juju agent version 2.9.29 for amd64
Located Juju agent version 2.9.29-ubuntu-amd64 at https://jujuagents.blob.core.windows.net/juju-agents/agents/agent/2.9.29/juju-2.9.29-linux-amd64.tgz
Launching controller instance(s) on azure/centralus...
- machine-0 (arch=amd64 mem=3.5G cores=1)
Installing Juju agent on bootstrap instance
Fetching Juju Dashboard 0.8.1
Waiting for address
Attempting to connect to 40.77.5.186:22
Attempting to connect to 192.168.16.4:22
Connected to 40.77.5.186
Running machine configuration script...
Bootstrap agent now started
Contacting Juju controller at 192.168.16.4 to verify accessibility...
Bootstrap complete, controller "arc-ubu" is now available
Controller machines are in the "controller" model
Initial model "default" added
-----
Deploy something with a few units:
-----
$ juju deploy ubuntu -n 10
Located charm "ubuntu" in charm-hub, revision 19
Deploying "ubuntu" from charm-hub charm "ubuntu", revision 19 in channel stable on focal
-----
At least one machine usually fails to provision. Snippit from the debug-log (full log attached):
-----
controller-0: 16:30:16 INFO juju.worker.instancepoller machine "7" (instance ID "machine-7") instance status changed from {"allocating" "starting"} to {"provisioning error" "The request failed due to conflict with a concurrent request. To resolve it, please refer to https://aka.ms/activitylog to get more details on the conflicting requests."}
-----
When I look at the activity log in the azure portal, i see "Create Deployment" has failed on the "Create or Update Availability Set" sub-task (see attached json).
Marking as critical as this seems like a regression due to the parallelisation of machine provisioning.
https:/