Forum Discussion
reddev12
Altocumulus
AltocumulusF5 os is upgrade but when in export template the image is not changed
We have Azure Vm with F5 os .
we upgrade the F5 to 15.1.8.1 from 15.1.6.1 .
And we exported the template after upgrade but the image info was not changed to new version .
Hi Suraj,
Not really my thing, but a while ago a customer asked me to prepare an Azure upgrade on their machines. I studied it but never went forward... but I do recall seeing a document stating you have to manually edit the ARM template.
Look at https://my.f5.com/manage/s/article/K31352754, step 4 in the "Edit the 'template.json' ARM template" section.
/Mike
- Mike757
MVP
Hi Suraj,
Not really my thing, but a while ago a customer asked me to prepare an Azure upgrade on their machines. I studied it but never went forward... but I do recall seeing a document stating you have to manually edit the ARM template.
Look at https://my.f5.com/manage/s/article/K31352754, step 4 in the "Edit the 'template.json' ARM template" section.
/Mike
reddev12Paulius I mean Azure template was exported after the upgrade .
But in Azure template the version of images was still 15.1.6.1 instead of 15.1.8.1 which was upgraded .
storageProfile": {"dataDisks": [],"imageReference": {"offer": "f5-big-ip-byol","publisher": "f5-networks","sku": "f5-big-all-2slot-byol","version": "15.1.601000" --------> This should change to new version 15.1.8.1Thankssuraj- Paulius
reddev12 My missunderstanding of the issue. So the device did upgrade correctly but when you extract the information it is showing the incorrect version in that extracted information? This could be an issue between Azure and the F5 VM. I know that in some instances in AWS (not Azure like you are stating) sometimes this data does take some time to populate correctly. If the profile does not update after some time has passed you will most likely have to open a ticket with Azure to resolve this issue.
