You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that after 2.1.7 was released, if there is a lesser version in the VM beforehand (in our case 2.1.6), the agent would uninstall the lesser version at startup and delete /var/lib/waagent/custom-script, which includes the new script that needs to be run.
Details:
Our setup is that we create a VM that runs a script using the custom script extension. The VM is converted into an Azure Compute Gallery image version, which is used for VMSS deployment in multiple regions. The VMSS deployment has a different script that we run using the custom script extension. The image version already has custom script extension installed (2.1.6) and the VMSS deployment is deployed in a region with a higher version (2.1.7). When the VMSS is deployed, the VMSS script is not run because the 2.1.6 version is uninstalled and deletes /var/lib/waagent/custom-script which includes the VMSS script, before 2.1.7 can run the script.
It seems that after 2.1.7 was released, if there is a lesser version in the VM beforehand (in our case 2.1.6), the agent would uninstall the lesser version at startup and delete /var/lib/waagent/custom-script, which includes the new script that needs to be run.
Details:
Our setup is that we create a VM that runs a script using the custom script extension. The VM is converted into an Azure Compute Gallery image version, which is used for VMSS deployment in multiple regions. The VMSS deployment has a different script that we run using the custom script extension. The image version already has custom script extension installed (2.1.6) and the VMSS deployment is deployed in a region with a higher version (2.1.7). When the VMSS is deployed, the VMSS script is not run because the 2.1.6 version is uninstalled and deletes /var/lib/waagent/custom-script which includes the VMSS script, before 2.1.7 can run the script.
/var/log/azure/custom-script/handler.log:
Is this intended? What would be the fix for this?
The text was updated successfully, but these errors were encountered: