[VM] vm image list --all returns all Marketplace URNs which vm create may not actually support

[voiddragon]

Hi there,

Creating VMs from Marketplace Images even if those are free require plan to be specified, I can't find an option for plans nor valid input for plan types.

az vm create --resource-group experimentsrg --name experiments-0 --image Bitnami:wordpress:4-4:4.6.14 --size Standard_A0 --storage-account 0293480239483204823

Command slightly redacted due to password in command

This was the error returned.

At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details. {
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMMarketplaceInvalidInput",\r\n "message": "Creating a virtual machine from Marketplace image requires Plan information in the request. OS disk name is osdisk14780645027063."\r\n }\r\n ]\r\n }\r\n}"
}
]
}
]
}
} Correlation ID: 541cfe31-cfbf-4696-ba06-598b8ccfb354

[tjprescott]

Hi @voiddragon thanks for bringing this issue to our attention!

It looks like, since this is a WordPress site, it needs a web hosting plan, which VM create does not expose. It is likely that other custom images in the marketplace with come with pre-installed software (as opposed to just an OS) might need other resources as well (SQL server, etc.) so we will need to evaluate this and decide how to proceed.

[tjprescott]

Hi @voiddragon. VM create is intended for creating VMs that are essentially blank except for the OS image. If you run az vm image list you will get the URNs for some common OS images that should all work with az vm create. There are also aliases for some of these, called out in az vm create -h. You can also provide a URI to an OS disk image VHD.

If you run az vm list --all you will get a list of all images from the Marketplace. Some of these will work, but many of them will not because they go beyond simply configuring a VM with an OS by having pre-installed software or configurations that require additional Azure resources beyond what az vm create is allowed to provision. In your case, because it is using WordPress, it requires an app service plan.

If you would like to create a Marketplace offering like the Bitnami image with WordPress that you tried, you should create that through the portal as it has a different engine that allows it prompt for those things.

@johanste In the meantime I will keep this issue open until we decide how to address the fact that az vm image list --all returns URNs which are not supported.

[JJ]

So I guess this is still open, right? Same problem here with

az vm create -g CCGroup -n bobot --image azul:azul-zulu-enterprise-ubuntu-1604:azul-zre-2016q3-ubtu1604:16.9.0

Basically, there seems to be no way to announce the plan you are using when you create a VM, right?

[yugangw-msft]

We should support this. I am also getting custom feedbacks on related failure when they tried to use Linux DSVM images. Suggestions on CLI:

1. We need to clearly show whether or not an image carries plan info (mainly cost related) that need to be supplied when create vm or vmss. vm image list/show should be enhanced to display this information easily.
2. On vm\vmss create, expose --plan or generic argument, so people can provide the value and get it created.

[lostintangent]

@yugangw-msft This would be amazing to get resolved! Many of the OSS images in the marketplace (e.g. Node.js) can't be provisioned via the CLI because of this issues.

[yugangw-msft]

I will submit a PR to fix this soon. No VM command interface change, and CLI will do the hard work to get things plumbed. The only piece I am not certain is whether I should expose the "promo-code". It is not because of the implementation difficulties, rather, to control the command complexity I try to avoid exposing dedicated args for things which are not much used by people, and I will count on #2281 to handle the rest.