simple streams failure - no 12.04 amd64 image in ap-southeast-2

Ian Booth ian.booth at canonical.com
Wed Jul 10 13:23:56 UTC 2013



On 10/07/13 23:11, Andreas Hasenack wrote:
> On Wed, Jul 10, 2013 at 3:38 AM, Ian Booth <ian.booth at canonical.com> wrote:
> 
>> The latest simplestreams metadata upload is broken. The latest data as of 2
>> hours ago is the culprit (around 10-Jul-2013 04:14 UTC)
>>
> 
> It's in situations like these that I miss the ability to specify the
> image-id I want juju to use in a simple and easy way.
> 
> 
> 

Sadly that would not have helped in this case as the default-image-id config
setting was only ever implemented for Openstack and not EC2 AFAIK. The reason it
was done for Openstack was that there was, until now, no image metadata
available with which the correct image could be chosen. EC2 had the metadata
from the start.

Allowing any arbitrary image id to be used opens up the real possibility that
the wrong one will be specified and not match the tools used. So the convenience
is outweighed by the possibility of breaking Juju in weird and hard to debug
ways, and the support costs that would entail.

We are engaging with the folks who publish the simplestreams metadata to put
processes in place to ensure this doesn't happen again.



More information about the Juju-dev mailing list