apache / libcloud

Apache Libcloud is a Python library which hides differences between different cloud provider APIs and allows you to manage different cloud resources through a unified and easy to use API.
https://libcloud.apache.org
Apache License 2.0
2.03k stars 925 forks source link

Unable to find a name for a VHD to use for instance #1471

Open moishikb opened 4 years ago

moishikb commented 4 years ago

Hi,

I'm trying to create a simple instance on Azure and I'm getting the exception as attached bellow. I tried to consult with Azure support but they didn't find something problematic with all definitions that related to my Azure account.

Please note that I'm getting the location, the size and the image properly from the defined driver.

**from libcloud.compute.types import Provider from libcloud.compute.providers import get_driver

cls = get_driver(Provider.AZURE_ARM) driver = cls(tenant_id=tenant_id, subscription_id=subscription_id, key=app_id, secret=secret) loc = [l for l in driver.list_locations() if l.id == default_zone ][0] size = [s for s in driver.list_sizes(location=loc) if s.name == base_instance_size ][0] ami = driver.get_image('Canonical:UbuntuServer:16.04-LTS:latest', location=loc) node = driver.create_node("test_node", ... size=size, ... image=ami, ... location=loc, ... ex_resource_group=resource_group, ... ex_storage_account=storage_account, ... ex_network='iavn1011126702', ... ex_subnet='iasub1011126702', ... auth=None)**

Traceback (most recent call last): File "", line 9, in File "/usr/local/lib/python3.6/dist-packages/libcloud/compute/drivers/azure_arm.py", line 600, in create_node ex_blob_container=ex_blob_container) File "/usr/local/lib/python3.6/dist-packages/libcloud/compute/drivers/azure_arm.py", line 2298, in _get_instance_vhd ("\n - ".join(errors))) libcloud.common.types.LibcloudError: <LibcloudError in None "Unable to find a name for a VHD to use for instance in 10 tries, errors were:

what can be the problem here?

Thanks, Moshik.

stale[bot] commented 3 years ago

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.