JeffGiroux
commented
4 years ago Here's a workaround:
############ ############ Workaround 1: edit JSON template
- search for available BIG-IP images in marketplace az vm image list -f big-ip --all
- Find your desired throughput (25Mb, 200Mb, 1Gb, etc)
- Find your desired consumption model (BYOL, PAYG)
- Find your desired version (14.1.200000, 14.1.202000, 14.1.203001)
- Update template and replace/add values for "bigIpVersion" with desired version
original...
"bigIpVersion": {
"allowedValues": [
"15.0.100000",
"14.1.200000",
"latest"
],
"defaultValue": "15.0.100000",
"metadata": {
"description": "F5 BIG-IP version you want to use."
},
"type": "string"
},after replacing value with 14.1.203001...
"bigIpVersion": {
"allowedValues": [
"15.0.100000",
"14.1.203001",
"latest"
],
"defaultValue": "15.0.100000",
"metadata": {
"description": "F5 BIG-IP version you want to use."
},
"type": "string"
},- Also edit template and replace value in "isAcceleratedNetworkingSupported" with false to make sure accelerated networking is disabled.
original...
"isAcceleratedNetworkingSupported": "[if(not(contains(parameters('bigIpVersion'), '14.1.200000')), bool('true'), bool('false'))]",after replacing with false (disables accelerated networking)...
"isAcceleratedNetworkingSupported": false, - Edit template one last time to replace a value in "bigIpVersionPortMap"
original...
"bigIpVersionPortMap": {
"15.0.100000": {
"Port": 8443
},
"14.1.200000": {
"Port": 8443
},
"443": {
"Port": 443
},
"latest": {
"Port": 8443
}
},after replacing value with 14.1.203001 (mgmt port 443 or 8443 depending on single-nic or multi-nic)...
"bigIpVersionPortMap": {
"15.0.100000": {
"Port": 8443
},
"14.1.203001": {
"Port": 8443
},
"443": {
"Port": 443
},
"latest": {
"Port": 8443
}
},- Deploy template and now 14.1.2.3 is a selectable option.
############ ############ Workaround 2: upgrade PAYG images after deployment (some caveats)
In my testing the PAYG images were able to go through an upgrade. There is only 1 boot slot created when you look in the BIG-IP GUI. If you do a upgrade in the GUI and select HD1 volume, then no options exist as only 1 boot slot was created. However, you can simply type the number "2" (without quote) and the upgrade will create boot slot 2 and install the upgraded BIG-IP version to new slot. **Caveat: Not all PAYG images for BIG-IP VE allow upgrade. For example the per app VE does not have enough disk space to do workaround 2.
vvt137
shyawnkarim
Do you already have an issue opened with F5 support?
No
Description
The latest minor release 14.1.2.3 of BIG-IP software was published on download.f5.com in Dec 2019 and is currently available in the set of f5-network marketplace images (e.g. URN f5-networks:f5-big-ip-good:f5-bigip-virtual-edition-25m-good-hourly:14.1.203001). Yet all ARM templates refer to 14.1.2.0 only. A workaround based on creating a custom image (and referring to it from the template) is possible for BYOL and BIG-IQ licensing, but not for PAYG implementations.
Ironically, it is the short-lived PAYG implementations that are affected the most as it is not practical to perform "classical" software update for them (and they would have benefited the most from using 1-slot images). Furthermore, PAYG per-app implementations are forced to remain on the 14.1.2.0 software (even if software-update overhead can be tolerated) as they cannot have the second slot.
Ideally, there would be the "latest" option for both major versions of stable software available via the template. I understand that it may be hard to achieve and the second best option is to keep updating the template as minor versions of "N-1" major release become available.
Template
The issue affects all BIG-IP templates, for example: https://github.com/F5Networks/f5-azure-arm-templates/tree/master/supported/standalone/2nic/existing-stack/payg
Severity Level
4