Closed tombuildsstuff closed 6 years ago
Hello!
Thank you for opening this issue and participating in the discussion. Today (December 19, 2017) we’ve announced the deprecation and archival of the Azure Classic Provider. Matching Microsoft’s commitment to gradually remove access to Azure Classic (or Service Management) which is outlined in this blog post, we are closing all open PR's and Issues here. This repository will remain available here on GitHub, but in an archived state, and no longer receiving support or new releases.
The Azure (Resource Manager) Provider remains fully supported and is our recommended approach for managing Azure with Terraform. More information about this process is available in the blog post linked above.
Thanks! The Terraform Team
Migrating this issue over to the Azure (Service Management) Provider repository as it was mis-tagged. This issue was originally opened by @nikitashalnov as hashicorp/terraform#11941. The original body of the issue is below.
Hello.
I just tried to play with terraform and create a test VM with the Linux Debian Jessie OS from a custom image. The custom image was captured from existed virtual machine by Azure Old Portal (https://manage.windowsazure.com).
But I'm getting an error:
I see that this image is in LEASE STATE Leased and in LEASE STATUS Locked. But this affects noting, because I can create a VM by Azure Cli as usual:
azure vm create mretailer-test-service jessie-template-2 nikita -l "West Europe" --ssh --no-ssh-password --ssh-cert /home/n.shalnov/azure_ssh.pem -w net -z ExtraSmall -v -n mretailer-test-service -b subnet-1 -S 10.11.11.68
Terraform successfully creates Cloud Service (resource azure_hosted_service) and fails on stage of creating a VM.
Here is more info.
Terraform Version
Terraform v0.8.6
Affected Resource
azure_instance
Terraform Configuration Files
There is my image:
It looks like a bug or maybe I'm wrong. If you need more information and something the written you didn't understand, please just tell me.