Share via

Stuck in Provisioning State: Updating

  • Article

Question

Tuesday, March 1, 2016 5:53 PM

H

I just moved my VMs to the ARM Deployment Model and now I am try to get familiar with starting and stopping the VMs with Azure Automation as f.e. shown here:

https://www.florinloghiade.ro/2015/12/sample-powershell-scripts-for-starting-and-stopping-azure-arm-vms-in-a-resource-group/

I am having some Issues with the Start-AzureRMVM CMDlet. The Start-AzureRMVM CMDlet is running forever until it is running into a timeout, as one of my VM is getting stuck in Provisioning State "Updating".

Actually the affected VM is up and running and I am also able to connect via RDP. But it is still in the Provisioning State: Updating.

How to resolve this issue?

All replies (3)

Friday, March 4, 2016 9:38 AM ✅Answered

Hi

1. VM is not deployed from Windows Server Image provided by Azure.
2. VHD has been copied to new ARM Storage Account, VM has been newly created from OS Disk.
3. Deallocating and reprovisioning does not Change anything..

But as the VM is up and running and just provisioning Status Shows "Updating", i decided to not care about that. Only Problem is that the Start-AzureRMVM CMDlet is running into a timeout as the provisioning state never changes to "ProvisionngState/succeded". 

Wednesday, March 2, 2016 10:58 AM

Hello Christian,

  1. Was this VM deployed from a custom image?
  2. How exactly did you move your VMs to ARM?

For the VMs created from customized images, the provisioning timed out error may occur if you upload an image that did not have sysprep with generalize run on it, or if there is an unattend.xml in the VHD conflicting with the unattend.xml that is on the ISO attached temporarily during provisioning stage.

Refer the link below which addresses similar concern: https://social.msdn.microsoft.com/Forums/azure/en-US/84a95986-481d-4583-b0f5-3af5b892fd11/vm-stuck-on-provisioning?forum=WAVirtualMachinesforWindows

You may try to stop (deallocate) the VM and check if that makes any difference.

What happens?   By stopping (deallocating) a VM, you not only stop the VM’s OS, you also free up the hardware and network resources Azure previously provisioned for it (a process called deallocation).

Important:  Things to know when the VM is shutdown (deallocated):

  1. By stopping (deallocating) a VM, you not only stop the VM’s OS, you also free up the hardware and network resources Azure previously provisioned for it (a process called deallocation).
  2. Unless you configured static addresses, you also release the internal DIP address, as well as the public VIP address (if no other VMs are using the public VIP, as the VIP is assigned to the cloud service and not directly to the virtual machine). When you restart the VM, it will then pick up a new public VIP (if it is not joining a cloud service that already has one) as well as a new DIP.
  3. The VM’s OS and data disks remain intact in Azure storage and can be used to restart the VM later. However, the temporary (scratch) disk associated with the VM is released and any data on that disk could be lost.

For more information on stopping-deallocating, please refer the link below: http://blogs.technet.com/b/uspartner_ts2team/archive/2014/10/10/azure-virtual-machines-stopping-versus-stopping-deallocating.aspx

Regards,
Ajay

Monday, March 14, 2016 3:34 PM

Hello Christian,

My apologies for the delayed response!

I have seen a similar issue when using a Premium Storage account with a non-Premium VM series. If you are using a Premium Storage account, you need to use either DS-Series or GS-Series of VMs.

For more details on this, please refer the link below:
https://azure.microsoft.com/en-in/documentation/articles/storage-premium-storage-preview-portal/

If you wish to further check the issue, you may consider opening a support ticket for more detailed analysis.

Request you to log a support ticket for the same 
http://azure.microsoft.com/en-us/support/options/

Regards,
Ajay