when version is missing on source VM VM is not created with an error of "Querying the image of 'null:null:null:null' failed for an error 'The value of parameter version is invalid."

[vilibert]

Using the BASH Linux VM Recovery script on a migrated VM gave an error of:

Querying the image of 'null:null:null:null' failed for an error 'The value of parameter version is invalid.'. Configuring plan settings will be skipped Deployment failed. Correlation ID: 7c7a0b44-f041-4b4f-99de-1d3e08391f23. {   "error": {     "code": "InvalidParameter",     "message": "The value of parameter imageReference.version is invalid.",     "target": "imageReference.version"   } }
--

This is because the script attempts to create a recovery VM based on the version of the source VM which on a migrated VM appears to be missing

A workaround was to use the PowerShell version of the script, which offers the ability to specify the Publisher and versions to be used for creating the Recovery VM.

These are the commands from PowerShell in Cloud Shell which force to create a recovery VM with Centos 7.5

./New-AzureRMRescueVM.ps1 -ResourceGroupName Source_VM_RG -VmName Source_vm_name -subscriptionId xxxxxx -offer CentOs -Publisher OpenLogic -sku 7.5 -Version 7.5.20180815 -UserName xxxxxx -Password xxxxxx

Ask: Integrate missing parameters into BASH Version (Publisher, sku, Version)

I suggest that logic is inserted into the script that if a version or other information is missing from the source VM, which prevents creation of a recovery VM then we should provide examples or the actual commands to create the recovery VM

or list the images and display them to customer
az vm image list --all --offer centos --output table

[d-sergienko]

Hi all,

Please find fix in this pull request: #13