Deploying failover/same-net/via-lb/3nic/existing-stack/byol/ - into Australia East consistently fails at the end of the deployment with VM has reported a failure when processing extension 'start'

joel-cloud commented 5 years ago

Do you already have an issue opened with F5 support?

no

Description

Azure deployment consistently fails with:

**

\"VM has reported a failure when processing extension 'start'. Error message: \\"Enable failed: processing file downloads failed: failed to download file[0]: failed to download file: http request failed: Get [REDACTED] dial tcp: i/o timeout **

What I am doing?

I'm trying to deploy a HA pair with LB into a prod subscription with existing subnets, after a lot of messing around i have the template deploying pretty much to the end. You can see the resource group and all the resource deployed, right at the end of the deployment something doesn't work and it fails. I would like the deployment to complete properly.

After the failed deployment, i can go and login to the F5's and configure them and everything works okay, however i would like the deployment to complete properly so we have confidence nothing was skipped .

BTW, because we are deploying into Australia East, we need to set the "zonesAvailable": false - everything else is as per the template.

Template

Using this template f5-azure-arm-templates/supported/failover/same-net/via-lb/3nic/existing-stack/byol/ deploying to a production subscription in Australia East.