- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Azure Cloudguard VMSS: Scaling Out does not pull d...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Azure Cloudguard VMSS: Scaling Out does not pull down the latest template
Hello,
I am having a weird problem. I have an R80.30 Cloudguard IaaS VMSS deployed in Azure. The current image version on them are R80.30.273-562
[Expert@xxx]# cat /etc/cloud-version
release: R80.30
take: 273
build: 562
I am told by checkpoint and have read in the documentation that when you scale-out it should update to the latest image. In this case R80.30-273.819. I even tried scaling-in to 0 then out again but no luck. The manager is also R80.30. I have another environment, that is my test environment, where it does work. The manager in my test environment is R80.20. The only difference I see so far is that my test environment uses byol and my other environment uses pay as you go license. What could cause this? What happens on the backend (in Azure) when a scale event occurs for which it is able to utilize the latest image?
Thanks in advance for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is that the version/build you initially built the VMSS with?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. I believe so. I had to always apply a hotfix via cpuse
![](/skins/images/BFDD56B372A07FDFABDEF003EE622D96/responsive_peak/images/icon_anonymous_message.png)