Quantcast
Channel: Azure Virtual Machines forum
Viewing all articles
Browse latest Browse all 12545

azure vm create does not work with a blob-url

$
0
0

Hi

Here is my command line

azure vm create "gfsgsfgfgsf" -o "vmdepot-21908-1-32" --location "West Europe" "AzureUser" "2;rVbUa%hu]+Ul;Qc18-9C" --ssh --vm-size "extrasmall" --blob-url "https://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgfgsf"

It is plainly impossible to make it works as shown in the output

C:\Users\NICO>azure vm create "gfsgsfgfgsf" -o "vmdepot-21908-1-32" --location"West Europe" "AzureUser" "2;rVbUa%hu]+Ul;Qc18-9C" --ssh --vm-size "extrasmal
l" --blob-url "https://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgf
gsf"
info:    Executing command vm create+ Looking up community image+ Looking up cloud service+ Creating cloud service
warn:    --location option will be ignored
warn:    --md5-skip, --parallel and/or --base-vhd options will be ignored
warn:    Any existing blob will be overwritten at https://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgfgsf
|warn:    Incorrect blob destination: https://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgfgsf
warn:    Using instead             : http://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgfgsf+  Copying image+ Looking up image vmdepot-21908-1-32-61928350+ Creating VM
info:    Deleting image
info:    VM image deleted: vmdepot-21908-1-32-61928350
info:    Blob deleted: http://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgfgsf+ Deleting cloud service
error:   A lease conflict occurred with the blob https://aotrainingtest.blob.core.windows.net/monitorvm/gfsgsfgfgsf.
error:   vm create command failed

By looking at the node source code, it seems that azure cli is downloading the blob image externally on blob-url, create the OS image from it, and then try to create a vm on this image by specifying the SourceImageName of the OS disk.

However, the bug seems to be that it also specify, the MediaLink to the same blob-url. When the deployment is running, it crashes because the blob is already leased by the image created earlier.

By the way, for now I'm using IaaS Management Studio instead of the CLI to create my vm, it works fine, but I stumbled on this problem when I was trying to add a feature to my tool to make it generates the azure cli command line.

Things works fine if I don't specify the blob-url, but if I do that, I can't choose where the OS disk is saved



Viewing all articles
Browse latest Browse all 12545

Trending Articles