none
Can't recreate virtual machine after usage limit was exceeded and now paid for RRS feed

  • Pergunta

  • I was using the free evaluation of Windows Azure Virtual Machines to see if my company could switch from our local cloud service providers to a Windows Azure. Today I've exceeded the usage limit (forgot to stop/delete one spurious VM created for testing only). The main VM was disconnected and its disk stored in storage account (which didn't exceeded the limit, as this is, after all, a test and usage is very low). Since I need the disk, and most importantly, the data inside it as it has performance information and even some production data that should never have ended up on that test VM, but... anyway, I'm not being able to:

    1) Reuse the old DNS. Even the VM being removed, when I try to create a new one and select the old DNS it tells me the old DNS is already in use (xpihomo.cloudapp.net)

    2) I can't create a virtual machine, it keeps getting me errors like this: "The server encountered an internal error. Please retry the request. The long running operation tracking ID was: 9439ecfa765c4d6d94bd9238a6e579a1."

    I'm also very disappointed that I only have a forum to ask for guidance and support. And can't imagine how I would proceed if this issue involved sensible information.

    segunda-feira, 12 de novembro de 2012 19:20

Respostas

  • I was able to resolve this issue by a very dirty, dirty route. Since it seemed that a lease conflict was preventing the VM from being mounted (certainly a bug in Azure's VM implementation) I've resorted to downloading a tool to manage the storage account and then I've copied the pertinent disk to another image and it worked. Here are the steps taken:

    1. Downloaded CloudXplorer evaluation (I'll certainly buy a license, because they've saved my skin)
    2. Connected to my storage account (using the keys informed in the web portal manager)
    3. Browsed to my storage and to the vhds container (the two VM disks were there, the one that worked and the one that didn't)
    4. created a new folder inside it named it 'Teste'
    5. copied the pertinent disk
    6. pasted the copied disk to the Teste folder
    7. Renamed the disk on the 'Teste' folder to something I want
    8. Cut the renamed disk from the 'Teste' folder
    9. Pasted the renamed disk back into the vhds 'root'
    10. Logged into the cloud management and went to Virtual Machines > Disks
    11. Used (+) CREATE DISK and choose the renamed disk above in the popup dialog
    12. Make sure to check "OS Disk" option and Windows.
    13. Created a new VM from the gallery, choosing my disk and using the above disk
    14. The VM was created succesfully
    • Marcado como Resposta frmachado segunda-feira, 12 de novembro de 2012 22:07
    segunda-feira, 12 de novembro de 2012 22:07

Todas as Respostas

  • I've also tried to create this message in the appropriate forum, but it seems that redirecting to pt-br forums missed up everything and the Virtual Machine forum is not accessible... I want to use the English-based forums, not the pt-br one, which seems like a scaled-down version of the English forums.
    segunda-feira, 12 de novembro de 2012 19:23
  • I was able to create another VM based on another disk. But it was not without issues: the same error occurred as before, but somehow, after 30 minutes or so, the VM was there, up and running. The problem is that this VM is not the one I need...
    segunda-feira, 12 de novembro de 2012 20:19
  • Just tried again to create the "correct" VM and got the same error: "The server encountered an internal error. Please retry the request. The long running operation tracking ID was: e0e7df56b33546ac931bfefd64869180."
    segunda-feira, 12 de novembro de 2012 20:22
  • As a last resort I've tried to attach the "important" VHD disk to the "unimportant" VM that I was able to recreate, but the following error occurred:

    A lease conflict occurred with the blob https://portalvhds4bqgghbw63gp9.blob.core.windows.net/vhds/lucasoft-eval-eval-vm-2012-10-25.vhd. The long running operation tracking ID was: 8b93b928645742b7ba49d196e10db472.

    So I'm really lost! There's nothing I can do. The VM can't be recreated from the disk and I can't attach the disk to another VM. And I'm paying for this! I've been already charged at U$ 2,75 without any of my VM actually working! What usage mileage is that?


    • Editado frmachado segunda-feira, 12 de novembro de 2012 20:38
    segunda-feira, 12 de novembro de 2012 20:37
  • I've found an answer for (1):

    When the VM instance is deleted the Cloud Service used to run it is not deleted automatically, and it keeps a hold on the DNS. If you want to reuse the same DNS you'll have to delete the cloud service entry... But would it delete the data from my VM? I don't think so, as it is stored in a separate VHD, but I just can't take the risk right now of deleting it...

    ... well... I've deleted the Cloude Services containers without issues, but I still can't recreate the VM with the appropriate disk. Only the "unimportant" VM, in the other disk, is working... Maybe Azure destroyed the data on my disk when it forcibly deleted the VM so now all my work on Windows Azure was lost.

    Now I'm getting this error when trying to recreate the VM:

    A lease conflict occurred with the blob https://portalvhds4bqgghbw63gp9.blob.core.windows.net/vhds/lucasoft-eval-eval-vm-2012-10-25.vhd. The long running operation tracking ID was: 46e41aa2ad404c7d99c88292544ba945.

    • Editado frmachado segunda-feira, 12 de novembro de 2012 21:07
    segunda-feira, 12 de novembro de 2012 20:58
  • I was able to resolve this issue by a very dirty, dirty route. Since it seemed that a lease conflict was preventing the VM from being mounted (certainly a bug in Azure's VM implementation) I've resorted to downloading a tool to manage the storage account and then I've copied the pertinent disk to another image and it worked. Here are the steps taken:

    1. Downloaded CloudXplorer evaluation (I'll certainly buy a license, because they've saved my skin)
    2. Connected to my storage account (using the keys informed in the web portal manager)
    3. Browsed to my storage and to the vhds container (the two VM disks were there, the one that worked and the one that didn't)
    4. created a new folder inside it named it 'Teste'
    5. copied the pertinent disk
    6. pasted the copied disk to the Teste folder
    7. Renamed the disk on the 'Teste' folder to something I want
    8. Cut the renamed disk from the 'Teste' folder
    9. Pasted the renamed disk back into the vhds 'root'
    10. Logged into the cloud management and went to Virtual Machines > Disks
    11. Used (+) CREATE DISK and choose the renamed disk above in the popup dialog
    12. Make sure to check "OS Disk" option and Windows.
    13. Created a new VM from the gallery, choosing my disk and using the above disk
    14. The VM was created succesfully
    • Marcado como Resposta frmachado segunda-feira, 12 de novembro de 2012 22:07
    segunda-feira, 12 de novembro de 2012 22:07