-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to deploy full stack failover example template with BYOL #40
Comments
Hi @tashian, can your BIG-IPs reach the public F5 license server? Are you using a proxy? See Error licensing: tryUntil: max tries reached: Unknown exception during ping for more info on that error. |
Thansk @mikeshimkus for the suggestions. I don't know exactly what is happening under the hood with Azure during the deployment, but to me this feels like a race condition. Just a hunch. 🤷🏻 |
Still seems to be a connectivity issue to the license server, which is odd since you were able to download the AT packages and config files and later you could reach the license server. I created task EC-510 and will see if I can repro, but it may end up being a Delclarative Onboarding issue since it seems to happen in the middle of DO configuration. |
@tashian I was able to eliminate the templates as a cause by deploying the same BYOL image directly from the marketplace and attempting to license via tmsh: azureuser@(localhost)(cfg-sync Standalone)(NO LICENSE)(/Common)(tmos)# install sys license registration-key XXXXX-XXXXX-XXXXX-XXXXX-XXXXXXX Please open a ticket with F5 support. I was not able to find an existing bug for this issue. |
Hi Mike, thanks for the repro. We (Smallstep) are F5 TAP program partners, and I'm unable to create a support ticket with my F5 login: I've sent an email to our TAP contact at F5 to let them know about the issue. Thanks |
Describe the bug
I've been trying to deploy a BYOL image with the failover template as an HA pair, and I'm getting an error during onboarding:
Error licensing: tryUntil: max tries reached: Unknown exception during ping ://:8080
Expected behavior
I expected the deployment to complete successfully.
Current behavior
The deployment fails with the following error:
Steps to reproduce
Important notes:
I used the
f5-networks:f5-big-ip-byol:f5-byol:17.1.101000
image URNI provided two license keys
I accepted the image terms by running
az vm image terms accept --urn f5-networks:f5-big-ip-byol:f5-big-all-2slot-byol:17.1.101000
I disabled the example demo web app
I used the default runtime init config YAML:
For Instance 1:
https://raw.githubusercontent.com/F5Networks/f5-azure-arm-templates-v2/v3.1.0.0/examples/failover/bigip-configurations/runtime-init-conf-2nic-byol-instance01.yaml
For Instance 2:
https://raw.githubusercontent.com/F5Networks/f5-azure-arm-templates-v2/v3.1.0.0/examples/failover/bigip-configurations/runtime-init-conf-2nic-byol-instance02.yaml
I didn't modify these because they looked okay for my use case.
I tried to revoke the license before deleting the resource group, but I ran into this error:
Here's the deployment template values:
Screenshots
The text was updated successfully, but these errors were encountered: