az image create is not working with a managed disk ID

[colemickens]

az image create -n nixos-image-16.09.1694.019dcc3-x86_64-linux.vhd -g aznixos --source /subscriptions/aff271ee-e9be-4441-b9bb-42f5af4cbaeb/resourceGroups/aznixos/providers/Microsoft.Compute/disks/nixos-image-16.09.1694.019dcc3-x86_64-linux.vhd --os-type linux

results in:

The URI /subscriptions/aff271ee-e9be-4441-b9bb-42f5af4cbaeb/resourceGroups/aznixos/providers/Microsoft.Compute/disks/nixos-image-16.09.1694.019dcc3-x86_64-linux.vhd does not look to be correct blob URI.

The examples clearly show creating an Image from a Managed Disk. Not sure what's going on.

[yugangw-msft]

Fix by #6220

[colemickens]

There's no chance that there is similar detection logic used in 'az vm create' is there? I saw some other weird behavior when I switched the disk name from "blah" to "blah.vhd" that also affected that command.

…

On Wed, Apr 25, 2018, 6:40 PM Yugang Wang ***@***.***> wrote: Fix by #6220 <#6220> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6227 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAT9dLHLGB8km1iEvjJ5IGwl_R6RvSGfks5tsSV5gaJpZM4TkXgL> .

[yugangw-msft]

let me cross check, which I should have done when I submitted the fix, but I forgot

[colemickens]

AFAICT this also affects az disk too:

$ az disk create -n nixos-image-16.09.1694.019dcc3-x86_64-linux-vhd -g aznixos --source https://aznixos.blob.core.windows.net/aznixos/nixos-image-16.09.1694.019dcc3-x86_64-linux-vhd --sku Premium_LRS
usage error: --source {SNAPSHOT | DISK} | --source VHD_BLOB_URI [--source-storage-account-id ID]

$ az disk create -n nixos-image-16.09.1694.019dcc3-x86_64-linux-vhd -g aznixos --source https://aznixos.blob.core.windows.net/aznixos/nixos-image-16.09.1694.019dcc3-x86_64-linux.vhd --sku Premium_LRS

[works]

Note the only difference is the blob having a -vhd or .vhd suffix. I had tried to change the suffix to work around this issue... and just ran into a different version of it. :/

[colemickens]

(This is because I have a single variable "TARGET" that is the blob name, the disk name, and the image name. So I'm either burnt because the disk/image name end in .vhd and confuse other commands, or I'm burnt because the blob won't end in .vhd and thus I won't be able to make a Disk out of it.)

[yugangw-msft]

Disk/snapshot/image were handled through the old PR this morning. The recent PR handles the vm and vmss

[colemickens]

Okay, didn't realize it got disk+image. Thanks so much, once again you fixed it hours (minutes maybe even) before I filed it. 😀 Looking forward to a new release. Thanks @yugangw-msft !