When deploying an custom Linux VHD on Azure V2 Resource manager with the json template on Github: 101-vm-from-user-image, the deployment failed after a while with the error:
statusMessage:{"status":"Failed","error":{"code":"ResourceDeploymentFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"VMStartTimedOut","message":"VM 'myVM' did not start in the allotted time. The VM may still start successfully. Please check the power state later."}]}}After this error we can't start the deployed VM. I am pretty sure that the Linux template VHD is not the problem, i use it successful on Azure V1, an also with the json template on Github: 201-vm-from-specialized-vhd. The major difference between the two json template is the way how the use the VHD template:
101-vm-from-user-image
"storageProfile": {
"osDisk": {
"name": "[concat(variables('vmName'),'-osDisk')]",
"osType": "[parameters('osType')]",
"caching": "ReadWrite",
"createOption": "FromImage",
"image": {
"uri": "[variables('userImageName')]"
},
"vhd": {
"uri": "[variables('osDiskVhdName')]"
}
}
201-vm-from-specialized-vhd
"name": "[concat(parameters('vmName'),'-osDisk')]",
"osType": "[parameters('osType')]",
"caching": "ReadWrite",
"vhd": {
"uri": "[parameters('osDiskVhdUri')]"
},
"createOption": "Attach"
}
The first one (witch causes the error) used the createOption fromImage, and the second one with succeed uses Attach method. Has anyone seen this problem before? Using the attach method is not very handy, because we have to upload/copy for every vm we used an vhd file (from the template).