azure provider sample config should default to East US

Bug #1251025 reported by Kapil Thangavelu on 2013-11-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

2013-11-13 21:15:00 DEBUG juju.environs.simplestreams simplestreams.go:936 finding products at path "streams/v1/"
2013-11-13 21:15:22 ERROR juju supercommand.go:282 cannot start bootstrap instance: POST request failed: BadRequest - The location or affinity group East US specified for source image b39f27a8b8c64d52b05eac6a62eba
d85__Ubuntu-12_04_3-LTS-amd64-server-20131111-en-us-30GB is invalid. The source image must reside in same affinity group or location as specified for hosted service West US. (http code 400: Bad Request)

because that's where the images are.

Kapil Thangavelu (hazmat) wrote :

so just in front of that in the logs is

2013-11-13 21:15:00 DEBUG juju.environs.simplestreams simplestreams.go:461 read metadata index at ""
2013-11-13 21:15:00 DEBUG juju.environs.simplestreams simplestreams.go:624 candidate matches for products ["" ""] are [{Tue, 12 Nov 2013 16:48:3
1 +0000 products:1.0 image-ids azure [{East Asia} {East US 2} {West Europe} {Southeast Asia https://ma} {East US} {Central US} {West US} {North Europe} {China East} {China North}] streams/v1/ [ com.]}]

Changed in juju-core:
status: New → Invalid
Curtis Hovey (sinzui) wrote :

We cannot do this at this time. only US West works. The issue relates to affinity groups. We have discussed placing tools in EVERY azure region, but I understand this should not be necessary.

tags: added: azure
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers