Azure bootstrap fails when 'location' and 'storage-account-name' are not in the same region
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The Juju Azure provider is currently configured to have the user specify the location in which they wish to deploy instances to, and the storage account to use with that deployed instances. Specifically, the environments.yaml keys are:
# Location for instances, e.g. West US, North Europe.
location: West US
# Windows Azure Storage info.
storage-
If the storage account is not in the same region as the instance than an error will occur. For example if the storage account is set up in West US but the user is trying to deploy instances to East US the user will get the following error:
2013-10-07 01:49:03 ERROR juju supercommand.go:282 cannot start bootstrap instance: POST request failed: BadRequest - The location or affinity group West US specified for source image b39f27a8b8c64d5
This is due to Azure trying to set an affinity group[0] and requires the storage and the instance be in the same region. A work around is to instruct the user to set up a storage account in each region they need to deploy to. One possible fix is to have Juju create the storage account for the user based on the region instances are being deployed to.
Example --debug bootstrap:
http://
[0] http://
-thanks,
Antonio
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: bootstrap |
tags: |
added: azure-provider removed: azure |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Forgot to mention these commands were run 1.15.1
arosales@x230:~$ juju --version
1.15.1-raring-amd64
-Thanks,
Antonio