-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Script Extensions timeout and I end up having to re-image the VM #26
Comments
One other related issue is the "Remove-AzureRmVmssExtension" delete operation never seems to finish. If I try to add the CSE back to the scaleset via the add-azurermvmssextension command I get this error: Update-AzureRmVmss : Operation 'PUT' is not allowed on VM extension 'DscClientExtension' since it is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete). |
Hi @andwie ... Did you get any solution to this issue ? |
What is your upgrade policy? |
Upgrade policy for SF cluster is set to automatic. |
This looks like a bug to me. Are you able to submit a support request? |
Hi. Similar issue. Renamed IaaSDiagnostics Extension type in ARM template. The old "named" extension is now causing CI/CD deployments to fail as deployment always times out. Trying to change the name back fails with get-azurermvmss shows the new named extension "VMDiagnosticsVmExt_vmNodeType0Name" as the only extension associated with the scaleset. |
Remove the existing extension and add it back with a new name.
|
vmss instances donot update after you uninstall cse extension. run below command and then add cse extension: |
Any update on this? Still having the issue when deploying with ARM templates |
The solution @avibha28 posted worked for me. After I ran that |
We have all our settings in ARM templates and each time we change a setting (add a NSG rule for example) we run New-AzureRmResourceGroupDeployment to create a new deployment and propagate the setting change to Test, Demo and then Production. I've found we sometimes get CSE (custom script extension) timeouts during this process on our VMs. Especially with the release of version 1.9 of custom script extension for windows. See the comments here for other folks encountering CSE issues:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/extensions-customscript
When this happens I have to delete the CSE via the Portal and re-run the deployment. Problem is you can't delete CSE objects for VM Scale Sets in the Azure Portal. I tried running the powershell below:
` $rpVMSS = Get-AzureRmVmss -ResourceGroupName "" -VMScaleSetName ""
But it errors out saying:
Update-AzureRmVmss : Long running operation failed with status 'Failed'.
ErrorCode: VMExtensionProvisioningError
ErrorMessage: Multiple VM extensions failed to be provisioned on the VM. Please see the VM extension instance view for details.
StartTime: 8/15/2017 11:52:17 AM
EndTime: 8/15/2017 11:52:20 AM
OperationID:
Status: Failed
At line:4 char:8
If I'm dealing with a regular VM I can easily delete the extension but if it is a scaleset VM I have to reimage the entire VM.
The text was updated successfully, but these errors were encountered: