Maintenance window configuration is not updating OSImage within the timeframe

Maulin Shah (Crest Data Systems Private Lim) 20 Reputation points Microsoft Vendor
2024-02-05T07:44:31+00:00

We have configured the maintenance configuration for all our VMSS with the scope of OSImage. so as per the expectation whenever we publish new image in our Shared Image gallery it should be replicate across the region and that should be picked by all the VMSS across all the subscription as per the maintenance window.

For now we are observing very uncertain behaviour for updating to the latest image across the VMSS using the enable automatic os upgrade. while checking the logs we didn't have a any concrete evidence of why it's not working. Any idea why it's not working?

Azure Virtual Machine Scale Sets
Azure Virtual Machine Scale Sets
Azure compute resources that are used to create and manage groups of heterogeneous load-balanced virtual machines.
332 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Prrudram-MSFT 20,856 Reputation points
    2024-02-08T06:07:19.34+00:00

    Hi @Maulin Shah (Crest Data Systems Private Lim)

    There could be several reasons why the automatic OS upgrade is not working as expected. Here are a few things you can check and let me know.

    Check if the VMSS is configured to use the latest version of the image in the Shared Image Gallery. You can do this by checking the "latest" tag in the image definition in the Shared Image Gallery.

    Check if the VMSS is configured to use the correct image definition in the Shared Image Gallery. You can do this by checking the "imageReference" property in the VMSS definition.

    Check if the VMSS is configured to use the correct update policy. You can do this by checking the "upgradePolicy" property in the VMSS definition.

    Check if the VMSS instances are healthy and able to receive the update. You can do this by checking the health status of the VMSS instances in the Azure portal.

    Check if there are any errors or warnings in the VMSS logs or in the Azure Activity Log. You can do this by checking the logs for the VMSS instances and the Azure Activity Log in the Azure portal.

    If you have checked all the above and are still experiencing issues, you may want to contact Microsoft support for further assistance. They can help you troubleshoot the issue and provide guidance on how to resolve it.

    --please don't forget to "[Accept the answer]" if the reply is helpful--